aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2023-04-14 11:30:20 -0700
committerAndres Freund <andres@anarazel.de>2023-04-14 11:30:33 -0700
commit43a33ef54e503b61f269d088f2623ba3b9484ad7 (patch)
treea43336dbc7ddae66a571ce4658f062b597c4d41f /contrib/postgres_fdw/postgres_fdw.c
parente4d905f772f7803d399b6e173ca9aa7ba8a35e5a (diff)
downloadpostgresql-43a33ef54e503b61f269d088f2623ba3b9484ad7.tar.gz
postgresql-43a33ef54e503b61f269d088f2623ba3b9484ad7.zip
Support RBM_ZERO_AND_CLEANUP_LOCK in ExtendBufferedRelTo(), add tests
For some reason I had not implemented RBM_ZERO_AND_CLEANUP_LOCK support in ExtendBufferedRelTo(), likely thinking it not being reachable. But it is reachable, e.g. when replaying a WAL record for a page in a relation that subsequently is truncated (likely only reachable when doing crash recovery or PITR, not during ongoing streaming replication). As now all of the RBM_* modes are supported, remove assertions checking mode. As we had no test coverage for this scenario, add a new TAP test. There's plenty more that ought to be tested in this area... Reported-by: Tom Lane <tgl@sss.pgh.pa.us> Reported-by: Alexander Lakhin <exclusion@gmail.com> Reviewed-by: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/392271.1681238924%40sss.pgh.pa.us Discussion: https://postgr.es/m/0b5eb82b-cb99-e0a4-b932-3dc60e2e3926@gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions