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 615b0a29-a859-b05a-46b6-45daf28bf685@postgresql.org
Whole thread Raw
In response to Re: Possible regression setting GUCs on \connect  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On 5/17/23 12:47 PM, Nathan Bossart wrote:
> On Wed, May 17, 2023 at 08:08:36AM -0400, Tom Lane wrote:
>> Amit Kapila <amit.kapila16@gmail.com> writes:
>>> Tom/Nathan, do you have any further suggestions here?
>>
>> My recommendation is to revert this feature.  I do not see any
>> way that we won't regret it as a poor design.
> 
> I agree.  The problem seems worth solving, but I think we ought to consider
> a different approach.  Apologies for not chiming in earlier on the original
> thread.

[RMT hat, personal opinion]

I do agree that the feature itself is useful, but given there is 
disagreement over the feature design, particularly from people who have 
spent time working on features and analyzing the security ramifications 
in this area, the safest option is to revert and try again for v17.

I suggest we revert before Beta 1.

Thanks,

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Possible regression setting GUCs on \connect
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: Memory leak from ExecutorState context?