From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Possible bug acldefault function |
Date: | 2025-03-19 15:45:20 |
Message-ID: | 707958.1742399120@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2025-03-19 17:11:07 | Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results |
Previous Message | Tom Lane | 2025-03-19 14:34:39 | Re: The != and +/- signs are joined together as an operator |