Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)
Date: 2019-10-11 20:44:23
Message-ID: CADK3HHLYODWpdSngdNCiH7S4=Exq7Kof00_t0oRjAJ6JTr+FQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 11 Oct 2019 at 16:41, Chapman Flack <chap(at)anastigmatix(dot)net> wrote:

> On 10/11/19 4:30 PM, Robert Haas wrote:
>
> > But, if it does need to be changed, it seems like a terrible idea to
> > allow it to be done via SQL. Otherwise, the user can break the driver
> > by using SQL to set the list to something that the driver's not
> > expecting, and there's nothing the driver can do to prevent it.
>
> ... unless there is something like a (perhaps more generally useful)
> BECAUSE I HAVE :cookie AND I SAY SO clause.[1]
>

Correct me if I'm wrong but I'm pretty sure nothing in the protocol
currently would allow this

While I see the utility at least for connection pools this does seem to be
scope creep at the moment

Dave

>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2019-10-11 20:53:53 Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)
Previous Message Chapman Flack 2019-10-11 20:41:20 Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)