25003
Read PG 18 manual ↗inappropriate_access_mode_for_branch_transaction
- SQLSTATE
- 25003
- Condition name
- inappropriate_access_mode_for_branch_transaction
- Class
- Invalid Transaction State
- Source macro
- ERRCODE_INAPPROPRIATE_ACCESS_MODE_FOR_BRANCH_TRANSACTION
- Evidence
- Definition only
English SQLSTATE atlas: authored explanations and source/runtime evidence are separate from the manual definitions. View source ↗
At a glance
25003 is the SQLSTATE name for an inappropriate access mode in a branch transaction. The fixed PostgreSQL 18.6 core scan resolves no direct report site, so this entry documents the definition boundary without inventing an ordinary SQL trigger.
Meaning
The condition name belongs to Class 25 and describes branch-transaction management. It should not be used as a synonym for 25006 read-only SQL transactions, 25P01 missing transaction blocks, or an application-defined exception.
Diagnosis
When this code is reported by a branch-transaction API, retain the exact SQLSTATE, API operation, access mode, and transaction context. The current fixed core evidence does not provide a server message template or a safe SQL reproduction.
Response
Inspect the branch-transaction API contract and correct its access-mode choice before retrying. Do not replace the missing path with RAISE, and do not retry a regular read-only statement under this code.
Source message and runtime boundary
The fixed errcodes.txt row defines the condition and macro; the resolved call scan in raw/calls/REL_18_6.jsonl contains no direct report group, so this batch publishes no message template and constructs no natural SQL trigger.
Applicability boundary and case
The selected runner cases on PostgreSQL 18.6 and 10.21 are not_applicable; they record the source boundary and contain no copyable SQL trigger. Structured evidence · case export
Versions and limits
The locked catalogue records the condition by the generated known present by boundary and in the listed snapshots. Runtime status is deliberately not applicable: both selected runner targets record the source-only boundary, not a passed natural trigger.
Sources
src.errcodes.18.6(SHA-2566e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba)src.calls.REL_18_6—raw/calls/REL_18_6.jsonl(SHA-2569ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf)
Source evidence
Evidence belongs to the frozen source and runtime versions listed here. It is not a runtime verification of the selected manual version.
25003 is inappropriate_access_mode_for_branch_transaction in Class 25.
Method: Read the fixed condition row and macro.
Limits: The name describes a branch-transaction access-mode condition; it is not a proof that ordinary SQL can raise it.
The exhaustive resolved PostgreSQL 18.6 call scan contains no direct 25003 report group, so this batch does not claim a natural SQL trigger or message template.
Method: Scan fixed source call records for SQLSTATE 25003.
Limits: An extension or a branch-transaction API may have a separate path; this page does not invent one.
- src/backend/utils/errcodes.txt · REL_18_6 ·
724edf9bde9d356724ad384a2e196edc3c9f80f7 raw/calls/REL_18_6.jsonl· ·
Message templates
No extracted message template is attached to this condition.
Reproduction & repair cases
branch_transaction_boundary · PG 10, 18
Preconditions
- A runner-owned disposable target is provisioned.
Trigger: Source/definition evidence only; no natural SQL trigger is claimed.
Expected assertions
- No fabricated SQL trigger is included; the selected run records a definition/source boundary.
Repair: Follow the explicit transaction or source boundary described by the case.
Cleanup: Drop the case schema with an owner connection.
Recorded runtime evidence
18.6 (Homebrew) · not_applicable
Run: 25003-batch2-latest-20260909
{
"case_status": "not_applicable"
}10.21 (Debian 10.21-1.pgdg90+1) · not_applicable
Run: 25003-batch2-pg10-20260909
{
"case_status": "not_applicable"
}Definition snapshot: english-manuals:60f8033b26b37207275325b89d4… · English manual source