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

From Alexander Korotkov
Subject Re: Possible regression setting GUCs on \connect
Date
Msg-id CAPpHfdtRHVYh+nPwehFua0vJ4=EVrTrc7pAAuBfBRcVHPf7DAA@mail.gmail.com
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
Re: Possible regression setting GUCs on \connect
List pgsql-hackers
Tom,

On Wed, May 17, 2023 at 3:08 PM Tom Lane <tgl@sss.pgh.pa.us> 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 have carefully noted your concerns regarding the USER SET patch that
I've committed.  It's clear that you have strong convictions about
this, particularly in relation to your plan of storing the setter role
OID in pg_db_role_setting.

I want to take a moment to acknowledge the significance of your
perspective and I respect that you have a different view on this
matter.  Although I have not yet had the opportunity to see the
feasibility of your approach, I am open to understanding it further.

Anyway, I don't want to do anything counter-productive.  So, I've
taken the decision to revert the USER SET patch for the time being.

I'm looking forward to continuing working with you on this subject for v17.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Fwd: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
Next
From: Kirk Wolak
Date:
Subject: Re: psql: Could we get "-- " prefixing on the **** QUERY **** outputs? (ECHO_HIDDEN)