0F000 — locator_exception
SQLSTATE 0F000 is the Locator Exception class. It is a category code, not a concrete locator failure message. The PostgreSQL 18.6 definition is present, but the locked core/contrib scan did not resolve a 0F000 report group. A client, embedded-SQL layer, extension, or remote implementation can still expose this standard class, so the observed producer must be identified before applying locator-specific advice.
English manual coverage begins with PostgreSQL 8.1. Source history and runtime observations have their own recorded version boundaries.
Reading PG 18·Select a recorded version
- aliases
- Unknown
- class name
- Locator Exception
- condition name
- locator_exception
- lang
- en
- sqlstate
- 0F000
Definition PG 18
0F000
At a glance {#at-a-glance}
SQLSTATE 0F000 is the Locator Exception class. It is a category code, not a concrete locator failure message. The PostgreSQL 18.6 definition is present, but the locked core/contrib scan did not resolve a 0F000 report group. A client, embedded-SQL layer, extension, or remote implementation can still expose this standard class, so the observed producer must be identified before applying locator-specific advice.
Meaning {#meaning}
The trailing 000 makes 0F000 a class-level condition. It groups locator-specific members such as 0F001; it does not identify a handle, descriptor, or locator operation by itself. PostgreSQL's definition row is useful for classification, while the fixed scan leaves the native emitting boundary unresolved.
Messages {#messages}
No fixed PostgreSQL message variant was adopted for this condition because the bounded scan did not resolve a native emitting call.
Diagnosis {#diagnosis}
Preserve the member SQLSTATE if one was returned, together with the client or server component, operation, and locator/descriptor identity. Search that component's fixed source or protocol mapping for the report path. Do not infer a locator handle from the class name, and do not treat a query that returned no rows as a locator exception.
Response {#response}
Repair the concrete locator or descriptor operation identified by the producing component, such as its lifetime, declaration, or referenced object, only when that component documents such a mechanism. If the result was forwarded from a remote system, preserve the remote error and use its owner’s recovery rules. No PostgreSQL-native retry rule is established for the category alone.
Versions {#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.
Related {#related}
Sources {#sources}
The fixed errcodes definition establishes the category and the SQLSTATE appendix describes condition classes. The locked core/contrib scan has no resolved native 0F000 report group. See the structured evidence record for fixed source paths, scan scope, and unresolved runtime boundaries.
Compare versions
SQLSTATE evidence and recorded runtime versions
claims · identity
{
"claim_id": "identity",
"limits": "",
"method": "Read the fixed errcodes definition row, severity, and macro.",
"position": 0,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "0F000 is locator_exception in SQLSTATE Class 0F."
}claims · scan-boundary
{
"claim_id": "scan-boundary",
"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.",
"method": "Compare resolved report groups with the fixed macro mapping.",
"position": 1,
"runtime": [],
"sources": [
"src.calls.REL_18_6",
"src.errcodes.18.6"
],
"statement": "No resolved 0F000 report group was found in the locked PostgreSQL 18.6 core/contrib call scan."
}claims · history-boundary
{
"claim_id": "history-boundary",
"limits": "Definition presence is not an emitting-path observation.",
"method": "Compare canonical release-definition facts with the available history boundary.",
"position": 2,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "The locked release definitions establish catalogue presence from the known 7.4 boundary; they do not establish a precise introducing release or runtime use."
}sources · src.errcodes.18.6
{
"commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
"docs_url": "",
"kind": "upstream_source",
"location": "",
"path": "src/backend/utils/errcodes.txt",
"position": 0,
"sha256": "6e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba",
"source_id": "src.errcodes.18.6",
"tag": "REL_18_6",
"url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt#L127"
}sources · src.calls.REL_18_6
{
"commit": "",
"docs_url": "",
"kind": "local_artifact",
"location": "",
"path": "raw/calls/REL_18_6.jsonl",
"position": 1,
"sha256": "9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf",
"source_id": "src.calls.REL_18_6",
"tag": "",
"url": ""
}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · english-manuals:14112f1ebc8da229e9a970664898ceeab21b8662907c8f45735084616df42ddb
Text language: en · english-manuals:14112f1ebc8da229e9a970664898ceeab21b8662907c8f45735084616df42ddb