# 57000 — operator_intervention

> Source-backed reference entry for PostgreSQL SQLSTATE 57000.
---

# 57000

## At a glance {#at-a-glance}
`57000` is the SQLSTATE Class 57 condition `operator_intervention`. The fixed 18.6 definition is present, but the bounded report/call scan did not resolve a core emitting call for this exact code. The page therefore keeps the mechanism, message, severity, and recovery boundary unresolved rather than assigning it to shutdown, timeout, or cancellation.

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

| Field | Value |
| --- | --- |
| SQLSTATE | `57000` |
| Condition | `operator_intervention` |
| 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_OPERATOR_INTERVENTION` |
| Aliases | `—` |

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

## Meaning {#meaning}
The condition name identifies an operator-intervention category, not a unique server phase. The fixed scan result is a bounded negative finding: it does not prove that no extension, future source path, or unresolved indirection can emit `57000`. No primary/detail/hint template is asserted from the fixed source, and no runtime observation is claimed.

## Diagnosis {#diagnosis}
Preserve the complete diagnostic from the provider: primary, detail, hint, severity, SQLSTATE, server version, connection state, and server-log correlation. Classify the concrete path from that message and surrounding logs. Do not infer administrator shutdown, statement cancellation, lock timeout, or startup refusal from the class name alone; those have distinct conditions and source paths.

## Response {#response}
Follow the operator or extension instruction carried by the actual response. If the session remains usable, resolve the named intervention and check whether an explicit transaction is still active; if the response is ERROR, issue `ROLLBACK` or `ROLLBACK TO SAVEPOINT` as appropriate before continuing. In autocommit, correct the cause before retrying. If the connection was terminated, reconnect only after server readiness and verify the business result before replaying a non-idempotent operation. The bounded scan supplies no more specific repair.

## Versions {#versions}
The locked catalogue records this condition from 7.4; that catalogue boundary does not prove the exact implementation-introduction version. Fixed source coverage is PostgreSQL 18.6, with a bounded report/call scan only.

## Related {#related}
[`55P03`](../55p03/), [`57P01`](../57p01/), [`57014`](../57014/)

## Sources {#sources}
[`src/backend/utils/errcodes.txt#L433`](https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt#L433)

The structured [evidence record](../data/evidence/57000.json) records the fixed definition, bounded scan artifact, and source/runtime boundary.