{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T10:49:29.433Z",
  "record_id": "VXI-EXT-PROCUREMENT-POSTGRES-DECODING-REPLAY-01-v1",
  "record_kind": "external_reference",
  "title": "PostgreSQL: Crash recovery can replay logical changes",
  "system": "PostgreSQL 18",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?",
  "near_questions": [
    "Which logical slot supplied the changes?",
    "When was its position checkpointed?",
    "Did the server restart after a crash?",
    "Could recent changes be sent again?",
    "What LSN did the consumer record?",
    "Are processing checkpoints durable?",
    "Does the slot know receiver completion?",
    "Can replay duplicate external effects?",
    "How are repeated changes handled?",
    "Was recovery tested separately?",
    "What uniqueness claim is supported?",
    "Can I save the logical-decoding review?"
  ],
  "supported_claims": [
    {
      "claim": "PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "PostgreSQL 18: Logical decoding concepts",
    "source_url": "https://www.postgresql.org/docs/18/logicaldecoding-explanation.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-POSTGRES-DECODING-REPLAY-01-v1",
    "candidate_record_sha256": "8714ac289e8a04d7658bdb5807595651163e9a638fd7ab12f1aaeaef645c22b1",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.",
    "required_buyer_context": "PostgreSQL version, logical slot position, crash window and consumer progress. Effective buyer configuration and operational results were not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?",
    "documented_statement": {
      "status": "documented",
      "statement": "PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.",
      "source_ids": [
        "postgres-decoding"
      ]
    },
    "buyer_evidence_required": [
      "Slot and last acknowledged log sequence position.",
      "Consumer durable processing checkpoint.",
      "Crash-recovery replay and duplicate-handling evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reconcile database replay position with consumer effects before asserting unique processing."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "postgres-decoding",
        "url": "https://www.postgresql.org/docs/18/logicaldecoding-explanation.html",
        "final_url": "https://www.postgresql.org/docs/18/logicaldecoding-explanation.html",
        "title": "PostgreSQL 18: Logical decoding concepts",
        "checked_on": "2026-10-17",
        "sha256": "9799a9ec5ecbccc49978416b7ae3959acbb28fa9b7acf4864f7251c1ba39c3a5",
        "bytes": 28842
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "PostgreSQL version, logical slot position, crash window and consumer progress."
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#postgres-logical-slot-crash-replay-consumer-state",
  "machine_readable_record": "/varexis-index/records/postgres-logical-slot-crash-replay-consumer-state.json"
}
