0F001
Read PG 18 manual ↗invalid_locator_specification
- SQLSTATE
- 0F001
- Condition name
- invalid_locator_specification
- Class
- Locator Exception
- Source macro
- ERRCODE_L_E_INVALID_SPECIFICATION
- Evidence
- Definition only
English SQLSTATE atlas: authored explanations and source/runtime evidence are separate from the manual definitions. View source ↗
At a glance
SQLSTATE 0F001 is the Invalid Locator Specification member of Class 0F. The locked PostgreSQL definition records the SQL-standard identity, but the resolved PostgreSQL 18.6 core/contrib scan did not find an emitting call. Do not turn the condition name into a claim about PostgreSQL large objects, cursors, FDW handles, or a particular driver API.
Meaning
The member identifies an invalid locator specification when the producing implementation uses the SQLSTATE. The fixed catalogue does not identify the locator representation or the operation that would be invalid in a current PostgreSQL backend. A member code is more specific than 0F000, but still needs its producer and message.
Messages
No fixed PostgreSQL message variant was adopted for this condition because the bounded scan did not resolve a native emitting call.
Diagnosis
Capture the full diagnostic and phase: parse/prepare, execution, descriptor lookup, or a client-side call. Identify the implementation that owns the locator and inspect its fixed documentation or source for accepted locator syntax and lifetime. If PostgreSQL returns another code, keep that code; the 0F001 definition is not a fallback classification.
Response
Correct the locator specification or its owning handle according to the producing implementation, then repeat only the failed statement when it is safe and no externally visible work was completed. For a forwarded or client-owned error, repair that boundary rather than changing PostgreSQL transaction policy from the condition name alone.
Versions
The locked catalogue places this condition at least by PostgreSQL 7.4. The release definitions cover the published snapshots listed in the facts block; source-path status is limited to the fixed PostgreSQL 18.6 context cited below.
Sources
The fixed errcodes definition establishes the member and macro; the SQLSTATE appendix provides the public class table. No resolved 0F001 report path was identified in the locked core/contrib scan. See the structured evidence record for fixed source paths, scan scope, and unresolved runtime boundaries.
Source evidence
Evidence belongs to the frozen source and runtime versions listed here. It is not a runtime verification of the selected manual version.
0F001 is invalid_locator_specification in SQLSTATE Class 0F.
Method: Read the fixed errcodes definition row, severity, and macro.
No resolved 0F001 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 an absolute absence claim.
The locked release definitions establish catalogue presence from the known 7.4 boundary; they do not establish a precise introducing release or runtime use.
Method: Compare canonical release-definition 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:865d2092c0d67edc93a8281e916… · English manual source