From: Tom Lane <tgl@sss.pgh.pa.us>
To: Inzamam Shafiq <inzamam.shafiq@hotmail.com>
cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: Possible bug acldefault function
In-reply-to: 
 <AM9P251MB0330304DEEE7015DEFBAB9D098D92@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
References: 
 <AM9P251MB0330304DEEE7015DEFBAB9D098D92@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
Comments: In-reply-to Inzamam Shafiq <inzamam.shafiq@hotmail.com>
	message dated "Wed, 19 Mar 2025 12:49:14 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <707957.1742399120.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Mar 2025 11:45:20 -0400
Message-ID: <707958.1742399120@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/707958.1742399120%40sss.pgh.pa.us>
Precedence: bulk

Inzamam Shafiq <inzamam.shafiq@hotmail.com> writes:
> I came across an issue while working with acldefault function on materia=
lized view, which threw an error "ERROR: unrecognized objtype abbreviation=
: m", when I looked at the source code of acldefault_sql it seems that mat=
erialized view case is not handled there, the SQL statement which I was ex=
ecuting is as follows,

No, acldefault doesn't consider 'm' to be valid input, because
materialized views are not a distinct kind of object for ACL purposes;
they're just relations (tables), and have relation-y privileges.

In fact, none of the object type codes accepted by acldefault_sql
are relkind values, except for the accidental overlap of 'r' with
the relkind for plain tables.

			regards, tom lane