]> granicus.if.org Git - postgresql/commit
Don't skip SQL backends in logical decoding for visibility computation.
authorAndres Freund <andres@anarazel.de>
Tue, 2 Dec 2014 22:42:26 +0000 (23:42 +0100)
committerAndres Freund <andres@anarazel.de>
Tue, 2 Dec 2014 22:52:44 +0000 (23:52 +0100)
commit10f1f93d8ae2d70fcaf350c62972fb6bac42ffc9
tree51190ad7c74945e07322cc5d4a7db6a8dcf1bd9c
parentf0eeba6f83ed16687d8743b34e519de45c3915ec
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.
contrib/test_decoding/expected/decoding_into_rel.out
contrib/test_decoding/sql/decoding_into_rel.sql
src/backend/replication/logical/logical.c
src/include/storage/proc.h