add transaction's final_lsn in each event #56
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.
In the cases where avoiding re-processing of events is mandatory
the consumer will need to have access to the LSN of the current transaction
For instance using a redis lock with an expire to avoid multiple workers to process the same event
or storing the latest LSN when a transaction is finished processing to know where the consumer shoud resume if it gets restarted (XXX/XXX start location in START_REPLICATION_SLOT)