Re: Possible regression setting GUCs on \connect

From: David Steele <david(at)pgmasters(dot)net>
To: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Possible regression setting GUCs on \connect
Date: 2023-04-27 16:35:25
Message-ID: e8c0fd08-ea2e-6878-2e94-910d9c447265@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/27/23 19:13, Tom Lane wrote:
> David Steele <david(at)pgmasters(dot)net> writes:
>> I have been updating pgAudit for PG16 and ran into the following issue
>> in the regression tests:
>> \connect - user1
>> WARNING: permission denied to set parameter "pgaudit.log_level"
>> This happens after switching back and forth a few times between the
>> current user when the regression script was executed and user1 which is
>> created in the script. Specifically, it happens at [1].
>
> If this is new in v16, I'm inclined to blame 096dd80f3, but that's
> just a guess without a test case.

Seems plausible. This can be reproduced by cloning [1] into contrib and
running `make check`. I can work out another test case but it may not
end up being simpler.

Thoughts on this Alexander?

[1] https://github.com/pgaudit/pgaudit/tree/dev-pg16-ci

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2023-04-27 17:35:20 Re: [PoC] Federated Authn/z with OAUTHBEARER
Previous Message Andres Freund 2023-04-27 16:27:43 Re: pg_stat_io for the startup process