2F004
Read PG 18 manual ↗reading_sql_data_not_permitted
- SQLSTATE
- 2F004
- Condition name
- reading_sql_data_not_permitted
- Class
- SQL Routine Exception
- Source macro
- ERRCODE_S_R_E_READING_SQL_DATA_NOT_PERMITTED
- Evidence
- Definition only
English SQLSTATE atlas: authored explanations and source/runtime evidence are separate from the manual definitions. View source ↗
At a glance
The catalogue defines this standard member, but the resolved PostgreSQL 18.6 core/contrib scan found no native report group. Do not infer a PostgreSQL function volatility or language rule from the condition name.
Meaning
2F004 describes a routine data-access restriction only when the producing implementation enforces it. A client, extension, ECPG layer, or remote routine engine may use the member independently.
Messages
No fixed PostgreSQL message variant was adopted because the bounded scan did not resolve a native report group.
Diagnosis
Record the routine owner, invocation phase, actual SQLSTATE, and declaration that limited reads. If the backend returned a different code, follow that code and its source path; the fixed catalogue row is not a fallback diagnosis.
Response
Apply only the producing implementation’s documented declaration or caller repair. No native PostgreSQL reporting path or generic retry boundary was confirmed for 2F004.
Versions
The locked catalogue places this condition at least by PostgreSQL 7.4. The facts block lists the published snapshots; source-path status is limited to the fixed PostgreSQL 18.6 evidence below.
Sources
See the fixed source links and message limits in the structured evidence record.
Source evidence
Evidence belongs to the frozen source and runtime versions listed here. It is not a runtime verification of the selected manual version.
2F004 is reading_sql_data_not_permitted in SQLSTATE Class 2F.
Method: Read the fixed errcodes definition row, severity, and macro.
No resolved 2F004 report group was found in the locked PostgreSQL 18.6 core/contrib call scan.
Method: Compare resolved report groups with the fixed macro mapping.
Limits: The scan does not cover external wrappers, drivers, extensions, remote systems, or user code; absence from this scan is not absolute.
Locked release definitions establish catalogue presence from 7.4; they do not establish a precise introducing release or runtime use.
Method: Compare canonical release facts with the available history boundary.
Limits: Definition presence is not an emitting-path observation.
- 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
No reproduction case is attached to this condition.
Recorded runtime evidence
No runtime observation is attached to this entry.
Definition snapshot: english-manuals:09bead9ac3b328b93ecbfc97718… · English manual source