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
