Fix lost updates with long running transactions #29
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.
The original c extension we aim to be a drop-in replacements
has a check to avoid insterting multiple history rows
in the same transaction
(see arkhipov/temporal_tables@b563fb3)
We kept this check in our port, but we introduced a bug in which
updated and deletes from all currently running transactions
may also be discarded, because we check
xmin
againsttxid_current_snapshot
.I fix it as suggested by @kjs222 on #27 by checking it only against
txid_current
.