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

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)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-08 15:52:00
Message-ID: CAMsr+YEcF9BhkOPALasAYyb9ckT-7K6e6wN-AEa0AxXqiRvZ9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 12 Jul 2019 at 01:27, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

>
> We have steadfastly refused to provide protocol-level tools for things
> like "please change my user ID, and don't let anyone change it again
> via SQL," and that's a huge problem for things like connection poolers
> which can't parse all the SQL flowing through the connection (because
> figuring out what it does requires solving the Halting Problem) and
> wouldn't want to if they could for performance reasons. I think that's
> a huge mistake.

I very strongly agree. The inability to limit SET and RESET of SESSION
AUTHORIZATION and ROLE is a huge pain point and it's far from the only one.

--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2019-10-08 15:57:24 Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)
Previous Message Mark Lorenz 2019-10-08 15:49:49 Re: Created feature for to_date() conversion using patterns 'YYYY-WW', 'YYYY-WW-D', 'YYYY-MM-W' and 'YYYY-MM-W-D'