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: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-07-11 19:15:55
Message-ID: CADK3HHLNZbGfR=-1vMJ9ri9RA+T7Vgyn0+8XG5PsK9itHEK9BQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 11 Jul 2019 at 15:07, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, Jul 11, 2019 at 2:29 PM Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> > So if I understand this correctly if user bob has altered his search
> path and there is a security-definer function called owned by him then
> > the search path will be changed for the duration of the function and
> reported for every iteration? The implications of this are "interesting" to
> say the least.
>
> I don't believe that it matters what search path has been set using
> ALTER USER bob.

Why wouldn't it ???

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2019-07-11 19:34:25 Re: initdb recommendations
Previous Message Robert Haas 2019-07-11 19:07:20 Re: base backup client as auxiliary backend process