Skip to content

docs(recovery): bind target observer operator handoff - #348

Draft
seonghobae wants to merge 25 commits into
fix/result-application-semantic-identifiersfrom
docs/postgres-recovery-target-observer-handoff
Draft

seonghobae wants to merge 25 commits into
fix/result-application-semantic-identifiersfrom
docs/postgres-recovery-target-observer-handoff

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Finding

PR #299's bounded recovery-target configuration observer has a cross-owner public/operator documentation contract. This PR owns only ADR 0019, physical/PITR doctoring and their focused documentation test; it does not own runtime/schema/provider authority.

Parent #324 is the canonical root architecture/product-gap documentation owner. Its latest change repairs a durable/mutable authority defect in docs/product-technical-gap-baseline.md; this descendant inherits that parent documentation through ordinary ancestry and does not duplicate it into recovery-owned files.

Exact topology

The parent change touches only the product-gap baseline, so the recovery-owned three-file slice remains lossless and non-overlapping.

Retained recovery contract

The handoff preserves exactly eight recovery-target settings plus pg_is_in_recovery(), bounded result materialization, fail-closed malformed/duplicate/unknown/oversized/pending-restart/inactive/mismatch handling, caller-owned connection/timeout policy and content-free provenance. Wrong-type or mutated PostgresPitrRecoveryTarget authority that no longer satisfies the reviewed contract is rejected before cursor acquisition/database I/O. PostgreSQL 18's effective recovery_target_inclusive=on default remains explicit when a reviewed name or immediate target has no inclusion edge; time/XID/LSN retain their explicit reviewed inclusion edge.

The seam does not create recovery.signal, provide restore_command, replay/validate WAL, prove archive completeness/timeline ancestry/target attainment, promote recovery, prove application readiness, or establish achieved RPO/RTO, HA/DR or certification.

Exact-current acceptance

The previous repository-local GREEN receipts on #348 0d8cca0e... and parent #324 056025a8... are predecessor evidence only after the parent and descendant moved. They do not transfer.

Fresh exact-current runs are nonterminal:

Keep Draft until this exact source generation obtains fresh terminal evidence and then-live review/governance requirements are satisfied.

Authority boundary

ADR 0019 remains Accepted only for the already-integrated bounded physical/PITR profile seam; the #299 observation handoff remains proposed until normally integrated. Moving central owner identities, workflow runs, queue state and review/governance topology are resolved from #244 and live central owners immediately before any integration decision rather than frozen into this durable recovery PR.

No wake/no-op commit, blind rerun, gate weakening, self-approval, administrator bypass, predecessor-evidence transfer, force update or destructive rebase is authorized. Refs #102, #109, #111, #121, #122, #184, #198, #200, #203, #204, #229, #233, #244, #278, #299, #306, #308, #309, #312, #316, #321, #324, #340, #341 and #345.

@coderabbitai

coderabbitai Bot commented Sep 16, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae seonghobae added documentation Improvements or additions to documentation priority: medium Normal-priority or P2 work labels Sep 19, 2026 — with ChatGPT Codex Connector
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation priority: medium Normal-priority or P2 work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant