0F000

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

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

No fixed PostgreSQL message variant was adopted for this condition because the bounded scan did not resolve a native emitting call.

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

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

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

0F001, 0A000

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.

Source evidence

Evidence belongs to the frozen source and runtime versions listed here. It is not a runtime verification of the selected manual version.

• 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.