{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-POSTGRES-PREPARED-RECOVERY-01-v1",
  "record_kind": "external_reference",
  "title": "PostgreSQL: Prepared transactions awaiting a decision",
  "system": "PostgreSQL",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does PostgreSQL PREPARE TRANSACTION mean a multi-system action has committed?",
  "near_questions": [
    "Is PREPARE TRANSACTION the final commit?",
    "Which PostgreSQL prepared transactions remain unresolved?",
    "Does a prepared transaction keep its locks?",
    "Who owns the two-phase commit recovery decision?",
    "What proves COMMIT PREPARED completed?",
    "Can an orphaned prepared transaction be assumed rolled back?",
    "Which participant decision is still missing?",
    "Where is the transaction-manager decision recorded?",
    "What does pg_prepared_xacts show?",
    "Can a prepared state establish global action completion?",
    "What evidence is needed before resolving an in-doubt transaction?",
    "Can INDEX resolve prepared PostgreSQL transactions?"
  ],
  "supported_claims": [
    {
      "claim": "PostgreSQL 18 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic distributed recovery or authority to force commit or rollback",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "PostgreSQL 18 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "PostgreSQL: PREPARE TRANSACTION",
    "source_url": "https://www.postgresql.org/docs/18/sql-prepare-transaction.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-POSTGRES-PREPARED-RECOVERY-01-v1",
    "candidate_record_sha256": "dce3addc66114f4e4ea983137f27c7adcd3f6ce5d1df4d0e04bfc652f4818a8b",
    "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 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.",
    "required_buyer_context": "Prepared transaction identifier, participant list and pg_prepared_xacts observations. Transaction-manager decision record and participant commit or rollback results. Retained locks, unresolved participants and authorized recovery ownership. 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": "Does PostgreSQL PREPARE TRANSACTION mean a multi-system action has committed?",
    "documented_statement": {
      "status": "documented",
      "statement": "PostgreSQL 18 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.",
      "source_ids": [
        "pg-prepare"
      ]
    },
    "buyer_evidence_required": [
      "Prepared transaction identifier, participant list and pg_prepared_xacts observations.",
      "Transaction-manager decision record and participant commit or rollback results.",
      "Retained locks, unresolved participants and authorized recovery ownership."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline global-completion claims or guessed resolution while the authoritative transaction-manager decision is missing."
    },
    "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-prepare",
        "url": "https://www.postgresql.org/docs/18/sql-prepare-transaction.html",
        "final_url": "https://www.postgresql.org/docs/18/sql-prepare-transaction.html",
        "title": "PostgreSQL: PREPARE TRANSACTION",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.203Z",
        "version_context": "PostgreSQL 18; two-phase commit prepared state",
        "sha256": "5826e134f6ec081922f213a467090515030a3211da9ffb5ec79635304cc3dcb1",
        "bytes": 19968,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Description; Notes; Caution"
        ]
      }
    ],
    "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 abandoned coordinator can leave blocked resources and an unresolved commit decision requiring deliberate 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": "Prepared transaction identifier, participant list and pg_prepared_xacts observations. Transaction-manager decision record and participant commit or rollback results. Retained locks, unresolved participants and authorized recovery ownership."
    },
    "buyer_relevance": "An abandoned coordinator can leave blocked resources and an unresolved commit decision requiring deliberate recovery.",
    "refusal_conditions": [
      "Decline global-completion claims or guessed resolution while the authoritative transaction-manager decision is missing."
    ]
  },
  "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-prepared-transaction-in-doubt-recovery",
  "machine_readable_record": "/varexis-index/records/postgres-prepared-transaction-in-doubt-recovery.json"
}
