Re: Extension pg_trgm, permissions and pg_dump order

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Färber, Franz-Josef (StMUK) <Franz-Josef(dot)Faerber(at)stmuk(dot)bayern(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Extension pg_trgm, permissions and pg_dump order
Date: 2022-05-27 19:32:37
Message-ID: 2722434.1653679957@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, May 27, 2022 at 2:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2022-05-27 23:13:32 Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
Previous Message Robert Haas 2022-05-27 19:29:07 Re: Extension pg_trgm, permissions and pg_dump order

Browse pgsql-general by date

  From Date Subject
Next Message Noah Misch 2022-05-28 04:51:22 Re: Extension pg_trgm, permissions and pg_dump order
Previous Message Robert Haas 2022-05-27 19:29:07 Re: Extension pg_trgm, permissions and pg_dump order