Re: Possible regression setting GUCs on \connect - Mailing list pgsql-hackers

From David Steele
Subject Re: Possible regression setting GUCs on \connect
Date
Msg-id e8c0fd08-ea2e-6878-2e94-910d9c447265@pgmasters.net
Whole thread Raw
In response to Re: Possible regression setting GUCs on \connect  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Possible regression setting GUCs on \connect
List pgsql-hackers
On 4/27/23 19:13, Tom Lane wrote:
> David Steele <david@pgmasters.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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_stat_io for the startup process
Next
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER