# 0F000 — locator_exception

> Source-bounded reference for PostgreSQL SQLSTATE 0F000.
---

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

<!-- BEGIN SQLSTATE FACTS: generated by scripts/generate.py; do not edit -->

| Field | Value |
| --- | --- |
| SQLSTATE | `0F000` |
| Condition | `locator_exception` |
| Status | `active` |
| Known present by | `7.4` |
| Locked snapshots | `9.0.23, 9.1.24, 9.2.24, 9.3.25, 9.4.26, 9.5.25, 9.6.24, 10.23, 11.22, 12.22, 13.23, 14.24, 15.19, 16.15, 17.11, 18.6, 19beta3` |
| Macros | `ERRCODE_LOCATOR_EXCEPTION` |
| Aliases | `—` |

<!-- source facts: data/errcodes/0F000.json -->
<!-- END SQLSTATE FACTS -->

## 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}

[`0F001`](../0f001/), [`0A000`](../0a000/)

## Sources {#sources}

The fixed [errcodes definition](https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt#L127) establishes the category and the [SQLSTATE appendix](https://www.postgresql.org/docs/18/errcodes-appendix.html) describes condition classes. The locked core/contrib scan has no resolved native 0F000 report group. See the structured [evidence record](../data/evidence/0f000.json) for fixed source paths, scan scope, and unresolved runtime boundaries.