P0000 — plpgsql_error

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.

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

8.1 8.2 8.3 8.4 9.0 9.1 9.2 9.3 9.4 9.5 9.6 10 11 12 13 14 15 16 17 18 19 20

aliases: Unknown
class name: PL/pgSQL Error
condition name: plpgsql_error
lang: en
sqlstate: P0000

Definition PG 18

P0000

At a glance {#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 {#meaning}

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

Diagnosis {#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 {#response}

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

Versions {#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.

Related {#related}

P0002, P0003, P0004

Sources {#sources}

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

Compare versions

SQLSTATE evidence and recorded runtime versions

claims · identity

{
  "claim_id": "identity",
  "limits": "",
  "method": "Read the fixed category row and macro.",
  "position": 0,
  "runtime": [],
  "sources": [
    "src.errcodes.18.6"
  ],
  "statement": "P0000 is plpgsql_error, the PostgreSQL-specific PL/pgSQL Error category entry."
}

claims · bounded-scan

{
  "claim_id": "bounded-scan",
  "limits": "A category definition does not imply that executor paths emit the category code itself.",
  "method": "Filter the archive by exact code and do not promote member-code reports to a category emitter.",
  "position": 1,
  "runtime": [],
  "sources": [
    "src.calls.REL_18_6"
  ],
  "statement": "The fixed REL_18_6 call archive has no resolved report group for the P0000 category code."
}

claims · member-boundary

{
  "claim_id": "member-boundary",
  "limits": "",
  "method": "Compare the category row with member definitions.",
  "position": 2,
  "runtime": [],
  "sources": [
    "src.errcodes.18.6"
  ],
  "statement": "Specific PL/pgSQL conditions such as P0002, P0003, and P0004 have their own report paths and should be diagnosed by their actual SQLSTATE."
}

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#L490"
}

sources · src.calls.REL_18_6

{
  "commit": "",
  "docs_url": "",
  "kind": "local_artifact",
  "location": "",
  "path": "raw/calls/REL_18_6.jsonl",
  "position": 1,
  "sha256": "9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf",
  "source_id": "src.calls.REL_18_6",
  "tag": "",
  "url": ""
}

Source references

Original manual reference

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · english-manuals:70f4b0f81adf8d60b53596e32a0efa3b9cba01bdc5edcda455571b8f623a9fb3

Text language: en · english-manuals:70f4b0f81adf8d60b53596e32a0efa3b9cba01bdc5edcda455571b8f623a9fb3