{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T17:54:06.066Z",
  "record_id": "VXI-EXT-PROCUREMENT-POSTGRES-RETRY-TRANSACTION-01-v1",
  "record_kind": "external_reference",
  "title": "PostgreSQL: Serialization failures and transaction retries",
  "system": "PostgreSQL",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "After a PostgreSQL serialization failure, is retrying only the last SQL statement sufficient?",
  "near_questions": [
    "Must PostgreSQL retry the entire transaction after 40001?",
    "Should the agent rerun the reads that selected its writes?",
    "Is this error a serialization failure or a persistent constraint violation?",
    "Does retrying the final INSERT restore the transaction decision?",
    "Which isolation level produced the failure?",
    "What identifies the replacement transaction attempt?",
    "Was the final COMMIT outcome retained?",
    "Can repeated contention prevent retry completion?",
    "Are external side effects outside the database transaction?",
    "Can Audit Coverage prove a database retry committed?",
    "Which application choices must be recomputed on retry?",
    "Does a successful retry prove external actions happened only once?"
  ],
  "supported_claims": [
    {
      "claim": "PostgreSQL 18 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic retry correctness, guaranteed progress or rollback and deduplication of effects outside the database transaction",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "PostgreSQL 18 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "PostgreSQL 18: Serialization Failure Handling",
    "source_url": "https://www.postgresql.org/docs/18/mvcc-serialization-failure-handling.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-POSTGRES-RETRY-TRANSACTION-01-v1",
    "candidate_record_sha256": "d2748cf6d64d24495ef9ba415f0d3b9ae8d3703fa3e744b82d54fbd1bfd8d90e",
    "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 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.",
    "required_buyer_context": "Isolation level, SQLSTATE and complete failed transaction boundary. Application decision logic and new attempt identity for the whole retry. Final commit result and separate reconciliation of any 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": "After a PostgreSQL serialization failure, is retrying only the last SQL statement sufficient?",
    "documented_statement": {
      "status": "documented",
      "statement": "PostgreSQL 18 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.",
      "source_ids": [
        "postgres-retry"
      ]
    },
    "buyer_evidence_required": [
      "Isolation level, SQLSTATE and complete failed transaction boundary.",
      "Application decision logic and new attempt identity for the whole retry.",
      "Final commit result and separate reconciliation of any external effects."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline recovery-complete claims from a statement-only replay; require the appropriate full transaction retry and final outcome evidence, without blindly retrying persistent errors."
    },
    "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-retry",
        "url": "https://www.postgresql.org/docs/18/mvcc-serialization-failure-handling.html",
        "final_url": "https://www.postgresql.org/docs/18/mvcc-serialization-failure-handling.html",
        "title": "PostgreSQL 18: Serialization Failure Handling",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T17:50:56.228Z",
        "version_context": "PostgreSQL 18, section 13.5",
        "sha256": "904f6f71968a9e64947f96d42f8c3da27e83faa9088523ddb9dcf4403e361c76",
        "bytes": 13464,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "PostgreSQL 18 section 13.5"
        ]
      }
    ],
    "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": "Agent recovery must preserve the transaction decision boundary and avoid treating every database error as an interchangeable transient failure.",
      "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": "Isolation level, SQLSTATE and complete failed transaction boundary. Application decision logic and new attempt identity for the whole retry. Final commit result and separate reconciliation of any external effects."
    },
    "buyer_relevance": "Agent recovery must preserve the transaction decision boundary and avoid treating every database error as an interchangeable transient failure.",
    "refusal_conditions": [
      "Decline recovery-complete claims from a statement-only replay; require the appropriate full transaction retry and final outcome evidence, without blindly retrying persistent errors."
    ]
  },
  "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-serialization-retry-whole-transaction",
  "machine_readable_record": "/varexis-index/records/postgres-serialization-retry-whole-transaction.json"
}
