aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts/sql/commit_timestamp.sql
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2016-11-24 15:39:55 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2016-11-24 15:39:55 -0300
commit9b66342901f2a3845fe2b44c647bb1316220975c (patch)
tree8935213ab71e106533e9083f7b5cb7f4f75bdbca /src/test/modules/commit_ts/sql/commit_timestamp.sql
parent4a5e1d3704e5922f7f457e5ccc6c4d4ac99c71db (diff)
downloadpostgresql-9b66342901f2a3845fe2b44c647bb1316220975c.tar.gz
postgresql-9b66342901f2a3845fe2b44c647bb1316220975c.zip
Fix commit_ts for FrozenXid and BootstrapXid
Previously, requesting commit timestamp for transactions FrozenTransactionId and BootstrapTransactionId resulted in an error. But since those values can validly appear in committed tuples' Xmin, this behavior is unhelpful and error prone: each caller would have to special-case those values before requesting timestamp data for an Xid. We already have a perfectly good interface for returning "the Xid you requested is too old for us to have commit TS data for it", so let's use that instead. Backpatch to 9.5, where commit timestamps appeared. Author: Craig Ringer Discussion: https://www.postgresql.org/message-id/CAMsr+YFM5Q=+ry3mKvWEqRTxrB0iU3qUSRnS28nz6FJYtBwhJg@mail.gmail.com
Diffstat (limited to 'src/test/modules/commit_ts/sql/commit_timestamp.sql')
0 files changed, 0 insertions, 0 deletions