Add recovery target reached hook with stop-boundary metadata PG16#64
Closed
GremSnoort wants to merge 2 commits into
Closed
Add recovery target reached hook with stop-boundary metadata PG16#64GremSnoort wants to merge 2 commits into
GremSnoort wants to merge 2 commits into
Conversation
Add a new RecoveryTargetReachedHook that is invoked after PostgreSQL reaches a recovery target and before recovery_target_action is applied. The hook receives a RecoveryTargetReachedInfo structure with the ReadRecPtr/EndRecPtr of the WAL record at the recovery stop boundary. This gives extensions an explicit recovery stop-boundary context for synchronizing or finalizing custom replay state before PostgreSQL exposes the target-reached state.
Contributor
|
same as #63 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add a new
RecoveryTargetReachedHookthat is invoked after PostgreSQL has determined that a recovery target has been reached, but beforerecovery_target_actionis applied.The hook receives explicit stop-boundary metadata via
RecoveryTargetReachedInfo, including:before/after)xid,time,LSN,name)ReadRecPtr/EndRecPtrfor the record at the stop boundaryProblem
PostgreSQL can reach a recovery target before an extension with custom replay/finalization logic has fully synchronized its own visible state to that same stop boundary.
In such cases, PostgreSQL already considers the target reached, but the extension-visible state may still lag behind the actual recovery stop point. This makes it difficult for extensions to guarantee correct target-point visibility semantics using only generic replay-progress information.
Motivation
Extensions with custom replay/finalization logic may need to synchronize their internal state against the actual recovery stop boundary before PostgreSQL exposes the target-reached state.
A generic replay-progress pointer is not always sufficient for this, especially for target types where extension-visible state must match the precise stop boundary semantics.
Changes
RecoveryTargetReachedInfoto carry recovery stop-boundary metadataRecoveryTargetReachedHookTypeRecoveryTargetReachedHookPerformWalRecovery()afterreachedRecoveryTargetand beforerecovery_target_actionis appliedResult
This gives extensions an explicit integration point for target-boundary synchronization/finalization without changing normal replay flow.
Issue
Closes: orioledb/orioledb#820