| From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX |
| Date: | 2022-12-15 09:42:00 |
| Message-ID: | a57d70af-032b-c8e3-c0a8-1f752b81ebdc@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.12.2022 03:27, Nathan Bossart wrote:
> Another option I'm looking at is skipping the privilege checks when VACUUM
> recurses to a TOAST table. This won't allow you to VACUUM the TOAST table
> directly, but it would at least address the originally-reported issue
This approach can be implemented for partitioned tables too. Skipping
the privilege checks when VACUUM/ANALYZE recurses to partitions.
> I don't know if this is good enough.
At least it's better than before.
> It seems like ideally you should be
> able to VACUUM a TOAST table directly if you have MAINTAIN on its main
> relation.
I agree, that would be ideally.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nitin Jadhav | 2022-12-15 10:12:00 | Re: Inconsistency in reporting checkpointer stats |
| Previous Message | Peter Eisentraut | 2022-12-15 09:32:27 | Re: static assert cleanup |