On Thu, 14 Dec 2023 at 02:13, Imseih (AWS), Sami 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.
>
>
>
> Th
> What is the actual
> use case for such a setting?
I don't have exact details on the use-case, bit this is not a common
use-case.
> Doesn't it risk security problems?
I cannot see how setting it on the database being more problematic than
setting it on a session level.
> I'm rather unimpress
"Imseih (AWS), Sami" writes:
> 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.
That seems like an extremely not-bright idea. What is
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
