From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Noah Misch <noah@leadboat.com>,
        =?UTF-8?B?RsOkcmJlciwgRnJhbnotSm9zZWYgKFN0TVVLKQ==?=
 <Franz-Josef.Faerber@stmuk.bayern.de>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Extension pg_trgm, permissions and pg_dump order
In-reply-to: 
 <CA+TgmoZ9BfWUTvfrcRa4jCGS9ca7XWhYNHPzwfojAu6n6st+Dg@mail.gmail.com>
References: <f8a4105f076544c180a87ef0c4822352@stmuk.bayern.de>
 <1961551.1653498155@sss.pgh.pa.us>
 <20220526055047.GA3153526@rfd.leadboat.com>
 <CA+TgmobJ31pKFAKJwq2p=4gKo_HYvYnnwJE7fz+T1auJfN+jEQ@mail.gmail.com>
 <2703829.1653677615@sss.pgh.pa.us>
 <CA+TgmoZ9BfWUTvfrcRa4jCGS9ca7XWhYNHPzwfojAu6n6st+Dg@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Fri, 27 May 2022 15:29:07 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2722433.1653679957.1@sss.pgh.pa.us>
Date: Fri, 27 May 2022 15:32:37 -0400
Message-ID: <2722434.1653679957@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2722434.1653679957%40sss.pgh.pa.us>
Precedence: bulk

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