{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-POSTGRES-ASYNC-COMMIT-DURABILITY-01-v1",
  "record_kind": "external_reference",
  "title": "PostgreSQL: Acknowledged commit before durable storage",
  "system": "PostgreSQL",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can PostgreSQL report a successful asynchronous commit that is lost in a subsequent crash?",
  "near_questions": [
    "Can an acknowledged PostgreSQL commit disappear after a crash?",
    "Was asynchronous commit enabled for this transaction?",
    "Did the WAL reach durable storage before failure?",
    "Is logical commit the same as crash durability?",
    "Can an external action rely on asynchronous commit success?",
    "What should be reconciled after PostgreSQL crash recovery?",
    "Does asynchronous commit imply database corruption?",
    "Which external effects depended on the lost transaction?",
    "Does a commit response establish recovered data state?",
    "What evidence shows the transaction survived restart?",
    "How does commit mode affect action assurance?",
    "Can INDEX verify PostgreSQL durability settings?"
  ],
  "supported_claims": [
    {
      "claim": "PostgreSQL 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof of durable storage, replica durability or validation of buyer database settings",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "PostgreSQL 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "PostgreSQL: Asynchronous commit",
    "source_url": "https://www.postgresql.org/docs/18/wal-async-commit.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-POSTGRES-ASYNC-COMMIT-DURABILITY-01-v1",
    "candidate_record_sha256": "ff296f3648266e9b0e3e7288f734ea5b137ab3ef281efb90cc5b9194b4e57317",
    "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 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.",
    "required_buyer_context": "Effective commit and durability settings for the transaction. Commit response, crash timeline and available WAL or recovery evidence. Post-recovery database state reconciled with dependent external effects. Buyer deployment 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": "Can PostgreSQL report a successful asynchronous commit that is lost in a subsequent crash?",
    "documented_statement": {
      "status": "documented",
      "statement": "PostgreSQL 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.",
      "source_ids": [
        "pg-async"
      ]
    },
    "buyer_evidence_required": [
      "Effective commit and durability settings for the transaction.",
      "Commit response, crash timeline and available WAL or recovery evidence.",
      "Post-recovery database state reconciled with dependent external effects."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline crash-durable completion claims without the applicable commit settings and recovered-state evidence."
    },
    "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": "pg-async",
        "url": "https://www.postgresql.org/docs/18/wal-async-commit.html",
        "final_url": "https://www.postgresql.org/docs/18/wal-async-commit.html",
        "title": "PostgreSQL: Asynchronous commit",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.238Z",
        "version_context": "PostgreSQL 18; asynchronous WAL flush durability",
        "sha256": "885d24ba8429035d22dce96b1f0b68e0263ff11800683c554f3795c13254476e",
        "bytes": 19534,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "28.4 Asynchronous Commit"
        ]
      }
    ],
    "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": "An agent may produce an irreversible external effect based on a database success that does not survive recovery.",
      "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": "Effective commit and durability settings for the transaction. Commit response, crash timeline and available WAL or recovery evidence. Post-recovery database state reconciled with dependent external effects."
    },
    "buyer_relevance": "An agent may produce an irreversible external effect based on a database success that does not survive recovery.",
    "refusal_conditions": [
      "Decline crash-durable completion claims without the applicable commit settings and recovered-state evidence."
    ]
  },
  "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-asynchronous-commit-crash-loss-boundary",
  "machine_readable_record": "/varexis-index/records/postgres-asynchronous-commit-crash-loss-boundary.json"
}
