Re: Extension pg_trgm, permissions and pg_dump order - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Extension pg_trgm, permissions and pg_dump order
Date
Msg-id 2722434.1653679957@sss.pgh.pa.us
Whole thread Raw
In response to Re: Extension pg_trgm, permissions and pg_dump order  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, May 27, 2022 at 2:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> From the security perspective it may be just fine.  Nonetheless,
>> we need to un-break pg_dump; it's not optional for that to work.

> That's pretty obvious. What's not obvious - at least to me - is
> whether the kinds of changes that Noah is proposing to make here have
> the effect of putting back the security vulnerability that the
> original commit was intended to fix.

Yeah, that is the problematic part of this.  I'm not sure about that
either, and we'll need to look at it closely.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Extension pg_trgm, permissions and pg_dump order
Next
From: Andres Freund
Date:
Subject: Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY