Re: [BUG] autovacuum may skip tables when session_authorization/role is set on database - Mailing list pgsql-hackers

From vignesh C
Subject Re: [BUG] autovacuum may skip tables when session_authorization/role is set on database
Date
Msg-id CALDaNm3NULfHAzVxc5D7CR=wYqo7uAEgsykK1qS3bZa2wU=xaw@mail.gmail.com
Whole thread Raw
In response to [BUG] autovacuum may skip tables when session_authorization/role is set on database  ("Imseih (AWS), Sami" <simseih@amazon.com>)
List pgsql-hackers
On Thu, 14 Dec 2023 at 02:13, Imseih (AWS), Sami <simseih@amazon.com> wrote:
>
> Hi,
>
>
>
> A recent case in the field in which a database session_authorization is
>
> altered to a non-superuser, non-owner of tables via alter database .. set session_authorization ..
>
> caused autovacuum to skip tables.
>
>
>
> The issue was discovered on 13.10, and the logs show such messages:
>
>
>
> warning:  skipping "table1" --- only table or database owner can vacuum it
>
>
>
> In HEAD, I can repro, but the message is now a bit different due to [1].
>
>
>
> WARNING:  permission denied to vacuum "table1”, skipping it
>
>
>
> It seems to me we should force an autovacuum worker to set the session userid to
>
> a superuser.
>
>
>
> Attached is a repro and a patch which sets the session user to the BOOTSTRAP superuser
>
> at the start of the autovac worker.

Since there is not much interest on this patch, I have changed the
status with "Returned with Feedback". Feel free to propose a stronger
use case for the patch and add an entry for the same.

Regards,
Vignesh



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: [PATCH] LockAcquireExtended improvement
Next
From: Bertrand Drouvot
Date:
Subject: Re: Synchronizing slots from primary to standby