Horton

Re: Extension pg_trgm, permissions and pg_dump order

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Noah Misch <noah@leadboat.com>, Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-27T18:53:35Z
Lists: pgsql-bugs, pgsql-general 
Robert Haas <robertmhaas@gmail.com> writes:
> Why isn't the current behavior - i.e. failing with a permissions error
> - correct? I mean I realize it's wrong in the sense that you can't
> restore a dump you just took, but what about from a security
> perspective?

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.

			regards, tom lane

Commits

  1. CREATE INDEX: use the original userid for more ACL checks.