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
Date: Wed, 19 Mar 2025 11:45:20 -0400
Message-ID: <707958.1742399120@sss.pgh.pa.us> (raw)
In-Reply-To: <AM9P251MB0330304DEEE7015DEFBAB9D098D92@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
References: <AM9P251MB0330304DEEE7015DEFBAB9D098D92@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
Inzamam Shafiq <inzamam.shafiq@hotmail.com> writes:
> I came across an issue while working with acldefault function on materialized view, which threw an error "ERROR: unrecognized objtype abbreviation: m", when I looked at the source code of acldefault_sql it seems that materialized view case is not handled there, the SQL statement which I was executing 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, inzamam.shafiq@hotmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Possible bug acldefault function
In-Reply-To: <707958.1742399120@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox