Horton

Re: Extension pg_trgm, permissions and pg_dump order

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Noah Misch <noah@leadboat.com>, pgsql-bugs@lists.postgresql.org, Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2022-06-03T18:17:24Z
Lists: pgsql-bugs, pgsql-general 
On Tue, May 31, 2022 at 08:28:55AM -0700, Nathan Bossart wrote:
> I've spent some time looking at all the code impacted by a117ceb and
> 0abc1a0, and I've yet to identify any additional problems besides the one
> with ResolveOpClass().  However, I'm far from confident in this analysis,
> and I still need to try out the ereport() approach that Noah suggested.  I
> would welcome any assistance identifying other problem areas.

Ah, I think I am missing something.  For example, the code that identifies
the exclusion operator (immediately following the call to ResolveOpClass())
is likely subject to a similar problem.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Commits

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