Fix incorrect xid and timestamp for continued txn COMMIT SQL. #302
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the missing
xid
andtimestamp
for continued transactions,This timestamp is used in
pgsql_replication_origin_xact_setup
which weupdate along with
COMMIT;
statement. So it makes more sense to putCOMMIT's
timestamp
as origin timestamp.Retaining the current update with
BEGIN
action as well. This avoidstimestamp
being empty forBEGIN
SQL statement in the file when COMMITspills to next SQL file.