↑↓ select ↵ open ⌫ change scope Open full search

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

SQLSTATE / CLASS P0 · PL/PGSQL ERROR

P0000

Read PG 18 manual ↗

plpgsql_error

SQLSTATE
P0000
Condition name
plpgsql_error
Class
PL/pgSQL Error
Source macro
ERRCODE_PLPGSQL_ERROR
Evidence
Definition only
Analysis & operational context

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

<h1>P0000</h1>

At a glance

P0000 is the PL/pgSQL Error category entry. The bounded PostgreSQL 18.6 call archive has no resolved report group for the category code itself, so member-code paths remain separate.

Meaning

This is a category identity for PL/pgSQL errors. More specific members such as P0002, P0003, and P0004 have their own paths.

Diagnosis

Use the actual SQLSTATE in the ErrorResponse and inspect the concrete PL/pgSQL path; do not assign a member error to the category code.

Response

Handle the concrete member SQLSTATE and its documented PL/pgSQL operation. Category identity alone is not enough for a narrower repair.

Versions

The locked catalogue records this condition from 8.0.0 in the listed formal snapshots and 19beta3; fixed source coverage is PostgreSQL 18.6.

Sources

See the fixed source links, message templates, and scope limits in the structured evidence record.

Source evidence

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

P0000 is plpgsql_error, the PostgreSQL-specific PL/pgSQL Error category entry.

Method: Read the fixed category row and macro.

src.errcodes.18.6

The fixed REL_18_6 call archive has no resolved report group for the P0000 category code.

Method: Filter the archive by exact code and do not promote member-code reports to a category emitter.

Limits: A category definition does not imply that executor paths emit the category code itself.

src.calls.REL_18_6

Specific PL/pgSQL conditions such as P0002, P0003, and P0004 have their own report paths and should be diagnosed by their actual SQLSTATE.

Method: Compare the category row with member definitions.

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