aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2014-12-02 23:42:26 +0100
committerAndres Freund <andres@anarazel.de>2014-12-02 23:47:08 +0100
commit0fd38e13706e6bd4b2a4ce4e0570d0aa4ad65345 (patch)
tree06761df2cd6448e02d42beb8f1ff15e0e5ad0643 /src/test/modules/commit_ts
parent75ef435218fe4f6ce29d33e10f6f7a328c93f7e7 (diff)
downloadpostgresql-0fd38e13706e6bd4b2a4ce4e0570d0aa4ad65345.tar.gz
postgresql-0fd38e13706e6bd4b2a4ce4e0570d0aa4ad65345.zip
Don't skip SQL backends in logical decoding for visibility computation.
The logical decoding patchset introduced PROC_IN_LOGICAL_DECODING flag PGXACT flag, that allows such backends to be skipped when computing the xmin horizon/snapshots. That's fine and sensible for walsenders streaming out logical changes, but not at all fine for SQL backends doing logical decoding. If the latter set that flag any change they have performed outside of logical decoding will not be regarded as visible - which e.g. can lead to that change being vacuumed away. Note that not setting the flag for SQL backends isn't particularly bothersome - the SQL backend doesn't do streaming, so it only runs for a limited amount of time. Per buildfarm member 'tick' and Alvaro. Backpatch to 9.4, where logical decoding was introduced.
Diffstat (limited to 'src/test/modules/commit_ts')
0 files changed, 0 insertions, 0 deletions