pgsql: Fix come incorrect elog() messages in aclchk.c - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Fix come incorrect elog() messages in aclchk.c
Date
Msg-id E1p8WUq-004xQb-U8@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix come incorrect elog() messages in aclchk.c

Three error strings used with cache lookup failures were referring to
incorrect object types for ACL checks:
- Schemas
- Types
- Foreign Servers
There errors should never be triggered, but if they do incorrect
information would be reported.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20221222153041.GN1153@telsasoft.com
Backpatch-through: 11

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/7ad458e06b1bf1408d9d089a843070943d6c7c6a

Modified Files
--------------
src/backend/catalog/aclchk.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Rename pg_dissect_walfile_name() to pg_split_walfile_name()
Next
From: Michael Paquier
Date:
Subject: Re: pgsql: Remove dead code