exclude empty ranges for RESTORE and REVERT #86
Merged
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.
Changing tables and columns multiple times during one transaction produces entries in log tables with
empty
txid_range. As noted in #81. In many cases this is covered by querying both the upper (NULL) and lower (NOT NULL) boundary of the range. But it was still missing in a few essential places, e.g. for restoring, reverting transactions,audit_tables
view.