Re: Possible regression setting GUCs on \connect

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible regression setting GUCs on \connect
Date: 2023-05-17 17:30:41
Message-ID: CAPpHfdtRHVYh+nPwehFua0vJ4=EVrTrc7pAAuBfBRcVHPf7DAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

On Wed, May 17, 2023 at 3:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

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