aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts/sql/commit_timestamp.sql
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2017-06-14 11:57:21 -0700
committerAndres Freund <andres@anarazel.de>2017-06-14 11:57:21 -0700
commit6c2003f8a1bbc7c192a2e83ec51581c018aa162f (patch)
treeba5318272f4c1995f736d0367315432bafeaa41f /src/test/modules/commit_ts/sql/commit_timestamp.sql
parentb6966d4627c0297ad42fe2592c66ac2f76e9962e (diff)
downloadpostgresql-6c2003f8a1bbc7c192a2e83ec51581c018aa162f.tar.gz
postgresql-6c2003f8a1bbc7c192a2e83ec51581c018aa162f.zip
Don't force-assign transaction id when exporting a snapshot.
Previously we required every exported transaction to have an xid assigned. That was used to check that the exporting transaction is still running, which in turn is needed to guarantee that that necessary rows haven't been removed in between exporting and importing the snapshot. The exported xid caused unnecessary problems with logical decoding, because slot creation has to wait for all concurrent xid to finish, which in turn serializes concurrent slot creation. It also prohibited snapshots to be exported on hot-standby replicas. Instead export the virtual transactionid, which avoids the unnecessary serialization and the inability to export snapshots on standbys. This changes the file name of the exported snapshot, but since we never documented what that one means, that seems ok. Author: Petr Jelinek, slightly editorialized by me Reviewed-By: Andres Freund Discussion: https://postgr.es/m/f598b4b8-8cd7-0d54-0939-adda763d8c34@2ndquadrant.com
Diffstat (limited to 'src/test/modules/commit_ts/sql/commit_timestamp.sql')
0 files changed, 0 insertions, 0 deletions