↑↓ select ↵ open ⌫ change scope Open full search

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

SQLSTATE / CLASS 0L · INVALID GRANTOR

0L000

Read PG 18 manual ↗

invalid_grantor

SQLSTATE
0L000
Condition name
invalid_grantor
Class
Invalid Grantor
Source macro
ERRCODE_INVALID_GRANTOR
Evidence
Source path confirmed
Analysis & operational context

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

<h1>0L000</h1>

At a glance

SQLSTATE 0L000 is invalid_grantor in Class 0L. The fixed aclparse path uses it as a backward-compatible warning when old ACL item text omits the /grantor suffix: it defaults the grantor to BOOTSTRAP_SUPERUSERID. This is ACL text parsing, not a bootstrap or ACL-initialization phase and not the ordinary “permission denied” or invalid GRANT-operation path.

Meaning

0L000 is invalid_grantor. In aclparse, an ACL item without a /grantor suffix takes a backward-compatibility fallback: the parser sets the grantor to BOOTSTRAP_SUPERUSERID and emits WARNING with SQLSTATE 0L000. This can occur while parsing ordinary ACL text; it does not identify bootstrap initialization. If a slash is present but no name follows it, the same parser instead raises 22P02 with a name must follow the "/" sign.

Diagnosis

If this warning appears, inspect the ACL text being parsed and whether it contains a grantor suffix. A missing slash and an empty name after a slash are different inputs: the first takes the 0L000 compatibility warning, while the second takes 22P02. A normal GRANT statement should be diagnosed with its concrete privilege or object error, such as 0LP01 or 42501.

Response

Preserve or rewrite serialized ACL text with an explicit valid grantor when the text is under your control, then review the resulting ACLs. Do not treat the warning as proof that bootstrap initialization failed. This page records the source path only; no natural SQL trigger is selected for 0L000.

Messages

The fixed omitted-grantor branch emits WARNING with 0L000 and primary defaulting grantor to user ID %u; the numeric user ID is dynamic. The adjacent slash-without-name branch emits ERROR with 22P02 and primary a name must follow the "/" sign. A client exception without the server diagnostic is not proof of 0L000.

Representative case

This page has no selected natural SQL run. The structured evidence records a source or definition boundary; a client-side RAISE would not represent a backend mechanism.

Versions

The generated facts table records the locked catalogue snapshots and earliest observed definition. This page has no selected natural SQL run; the fixed REL_18_6/REL_10_23 aclparse source comparison must not be read as an observed runtime result or as a claim about every intermediate release.

Sources

  • src.aclparse-grantor-fallback.18.6 — src/backend/utils/adt/acl.c at REL_18_6 commit 724edf9bde9d356724ad384a2e196edc3c9f80f7; fixed blob SHA-256 623f2dd01c1d393d3b224c7622dc2ec946faced444c1f5fd5e396e037903a5b0 (source). This is the aclparse omitted-grantor compatibility branch.
  • src.aclparse-grantor-fallback.10.23 — src/backend/utils/adt/acl.c at REL_10_23 commit 02991e79f8f58bc208f05dcc8af0c62dbe0a6ea4; fixed blob SHA-256 3cfe29c06d211130552d2aab88f61dcdd9a5287c9ab8c450d48562056b32829e (source). This is the aclparse omitted-grantor compatibility branch.
  • src.aclparse-slash-missing-name.10.23 — the same fixed acl.c blob, lines 338–344, records the separate 22P02 branch when / is followed by no name (source).
  • src.calls.REL_18_6 / src.calls.REL_10_23 — fixed local call scans, SHA-256 9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf / 00d16d3eb01b71ccf1b245c8f3102f9d0ec9f36fb02777b8dd1b99fcb263040c; these scans preserve the resolved call context used by the claims.

Source evidence

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

0L000 is the invalid_grantor condition in Class 0L.

Method: Read the fixed errcodes.txt definition and the locked catalogue metadata.

Limits: Directory identity does not identify every backend or client path.

src.errcodes.18.6

The fixed aclparse path accepts ACL item text without a /grantor suffix for backward compatibility, defaults the grantor to BOOTSTRAP_SUPERUSERID, and emits WARNING 0L000. If a slash is present but no name follows it, the parser instead emits 22P02; this is ACL text parsing rather than bootstrap or ACL initialization and is not an ordinary GRANT failure.

Method: Read the complete fixed aclparse branch in REL_18_6 and REL_10_23, including the slash-without-name error branch and the omitted-grantor fallback.

Limits: This is a bounded source claim; no natural SQLSTATE case was selected, and the warning's numeric user ID is dynamic.

src.aclparse-grantor-fallback.18.6 src.aclparse-grantor-fallback.10.23 src.aclparse-slash-missing-name.10.23

The locked catalogue records 0L000 in the listed snapshots; this page compares only the fixed REL_18_6 and REL_10_23 aclparse source paths and has no selected natural runtime.

Method: Read the generated facts block and fixed aclparse source records; no runtime result is used for this source-only page.

Limits: Presence in a definition file is not an exact behavioral introduction, and the fixed source paths do not prove every intermediate release.

src.errcodes.18.6 src.aclparse-grantor-fallback.18.6 src.aclparse-grantor-fallback.10.23

Message templates

explicit WARNING · message.aclparse-grantor-fallback

Primary

defaulting grantor to user ID %u

The %u value is BOOTSTRAP_SUPERUSERID in the fixed fallback branch; this message is emitted for ACL text without a /grantor suffix.

explicit ERROR · message.aclparse-slash-missing-name

Primary

a name must follow the "/" sign

Reproduction & repair cases

source_boundary · PG 10, 18

Preconditions

  • A runner-owned disposable target is provisioned only if a source-boundary smoke run is requested.

Trigger: No artificial SQL trigger is executed; this record preserves the fixed source/definition boundary.

Expected assertions

    Repair: Use the concrete source path or component-specific documentation when it applies.

    Cleanup: Drop the case schema with an owner connection.

    Recorded runtime evidence

    No runtime observation is attached to this entry.

    Definition snapshot: english-manuals:072a2f348467f5643e41b6be02a… · English manual source