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

From Jonathan S. Katz
Subject Re: Possible regression setting GUCs on \connect
Date
Msg-id 04b70513-bb02-1406-2430-35a4daa6dedc@postgresql.org
Whole thread Raw
In response to Re: Possible regression setting GUCs on \connect  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Possible regression setting GUCs on \connect  (Pavel Borisov <pashkin.elfe@gmail.com>)
List pgsql-hackers
On 4/27/23 8:04 PM, Alexander Korotkov wrote:
> On Fri, Apr 28, 2023 at 2:30 AM Alexander Korotkov <aekorotkov@gmail.com> wrote:
>> Additionally, I think if we start recording role OID, then we need a
>> full set of management clauses for each individual option ownership.
>> Otherwise, we would leave this new role OID without necessarily
>> management facilities.  But with them, the whole stuff will look like
>> awful overengineering.
> 
> I can also predict a lot of ambiguous cases.  For instance, we
> existing setting can be overridden with a different role OID.  If it
> has been overridden can the overwriter turn it back?

[RMT hat]

While the initial bug has been fixed, given there is discussion on 
reverting 096dd80f3, I've added this as an open item.

I want to study this a bit more before providing my own opinion on revert.

Thanks,

Jonathan



Attachment

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Autogenerate some wait events code and documentation
Next
From: Eric Ridge
Date:
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames