↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

SQLSTATE / CLASS 57 · OPERATOR INTERVENTION

57000

Read PG 18 manual ↗

operator_intervention

SQLSTATE
57000
Condition name
operator_intervention
Class
Operator Intervention
Source macro
ERRCODE_OPERATOR_INTERVENTION
Evidence
Definition only
Analysis & operational context

English SQLSTATE atlas: authored explanations and source/runtime evidence are separate from the manual definitions. View source ↗

<h1>57000</h1>

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

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

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

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

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.

Sources

src/backend/utils/errcodes.txt#L433

The structured evidence record records the fixed definition, bounded scan artifact, and source/runtime boundary.

Source evidence

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

57000 is operator_intervention in SQLSTATE Class 57.

Method: Read fixed definition.

src.errcodes.18.6

The bounded PostgreSQL 18.6 source scan did not resolve a fixed core emitting path for this condition.

Method: Read the fixed definition and the bounded REL_18_6 report/call scan.

Limits: This does not prove that no extension, future path, or unresolved call can emit the condition.

src.errcodes.18.6 scan.calls.REL_18_6

The locked catalogue records 57000 from 7.4; that boundary does not prove exact implementation introduction.

Method: Use catalogue boundary.

src.errcodes.18.6

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.

Definition snapshot: english-manuals:009b835b12c9d90c6bf39049eb9… · English manual source