↑↓ select ↵ open ⌫ change scope Open full search

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

SQLSTATE / CLASS 2F · SQL ROUTINE EXCEPTION

2F000

Read PG 18 manual ↗

sql_routine_exception

SQLSTATE
2F000
Condition name
sql_routine_exception
Class
SQL Routine Exception
Source macro
ERRCODE_SQL_ROUTINE_EXCEPTION
Evidence
Definition only
Analysis & operational context

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

<h1>2F000</h1>

At a glance

SQLSTATE 2F000 is the SQL Routine Exception category. The definition is present in the locked catalogue, but the resolved PostgreSQL 18.6 core/contrib call scan did not identify a native 2F000 report group. The class should therefore organize routine-related investigation; it does not identify a particular function declaration, PL/pgSQL statement, or retry rule.

Meaning

2F000 is a category code. Its member 2F002 names one standard routine data-access restriction, but a member path must be confirmed separately. PostgreSQL can report other routine errors with different SQLSTATEs; retain the returned member, message, routine, and server version instead of replacing them with the category.

Messages

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

Diagnosis

Record whether the failure occurred while creating, invoking, or executing a routine, and identify the owner (backend, extension, ECPG, driver, or remote server). Search the fixed implementation for the exact member and message. A category-only observation is insufficient to infer whether a data-access rule, argument error, or routine body caused it.

Response

Apply the repair documented by the producing routine implementation and its member SQLSTATE. If a remote or client layer produced the condition, repair that owner’s declaration or call contract. Do not retry a routine category without knowing whether execution began or completed.

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.

Sources

The fixed errcodes definition establishes the category and the SQLSTATE appendix lists its members. No resolved native 2F000 report group was found in the locked core/contrib call scan. 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.

2F000 is sql_routine_exception in SQLSTATE Class 2F.

Method: Read the fixed errcodes definition row, severity, and macro.

src.errcodes.18.6

No resolved 2F000 report group was found in the locked PostgreSQL 18.6 core/contrib call scan.

Method: Compare resolved report groups with the fixed macro mapping.

Limits: The scan does not cover external wrappers, drivers, extensions, remote systems, or user code; absence from this scan is not an absolute absence claim.

src.calls.REL_18_6 src.errcodes.18.6

The locked release definitions establish catalogue presence from the known 7.4 boundary; they do not establish a precise introducing release or runtime use.

Method: Compare canonical release-definition facts with the available history boundary.

Limits: Definition presence is not an emitting-path observation.

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:7f9813a4eac9fc78e0294d270f5… · English manual source