57000 — operator_intervention
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.
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
- Operator Intervention
- condition name
- operator_intervention
- lang
- en
- sqlstate
- 57000
Definition PG 18
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.
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}
Sources {#sources}
src/backend/utils/errcodes.txt#L433
The structured evidence record records the fixed definition, bounded scan artifact, and source/runtime boundary.
Compare versions
SQLSTATE evidence and recorded runtime versions
claims · identity
{
"claim_id": "identity",
"limits": "",
"method": "Read fixed definition.",
"position": 0,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "57000 is operator_intervention in SQLSTATE Class 57."
}claims · scan-boundary
{
"claim_id": "scan-boundary",
"limits": "This does not prove that no extension, future path, or unresolved call can emit the condition.",
"method": "Read the fixed definition and the bounded REL_18_6 report/call scan.",
"position": 1,
"runtime": [],
"sources": [
"src.errcodes.18.6",
"scan.calls.REL_18_6"
],
"statement": "The bounded PostgreSQL 18.6 source scan did not resolve a fixed core emitting path for this condition."
}claims · history
{
"claim_id": "history",
"limits": "",
"method": "Use catalogue boundary.",
"position": 2,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "The locked catalogue records 57000 from 7.4; that boundary does not prove exact implementation introduction."
}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#L433"
}sources · scan.calls.REL_18_6
{
"commit": "",
"docs_url": "",
"kind": "local_artifact",
"location": "",
"path": "raw/calls/REL_18_6.jsonl",
"position": 1,
"sha256": "9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf",
"source_id": "scan.calls.REL_18_6",
"tag": "",
"url": ""
}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · english-manuals:2fb22447e2163200c6e42517023b25451f5d29c4f8971ed725e822ba706bf9ca
Text language: en · english-manuals:2fb22447e2163200c6e42517023b25451f5d29c4f8971ed725e822ba706bf9ca