pgsql: Fix come incorrect elog() messages in aclchk.c

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix come incorrect elog() messages in aclchk.c
Date: 2022-12-23 01:05:13
Message-ID: E1p8WUq-004xQk-VY@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/df6fea51f01d38a427ed7c5d2e13c501f0beb4f0

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

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-12-23 01:05:49 Re: pgsql: Remove dead code
Previous Message Michael Paquier 2022-12-23 00:20:37 pgsql: Rename pg_dissect_walfile_name() to pg_split_walfile_name()