Re: Extension pg_trgm, permissions and pg_dump order

Noah Misch <noah@leadboat.com>

From: Noah Misch <noah@leadboat.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, 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-13T03:45:51Z
Lists: pgsql-bugs, pgsql-general
On Wed, Jun 08, 2022 at 10:17:08PM -0700, Noah Misch wrote:
> On Sun, Jun 05, 2022 at 11:30:56PM -0700, Noah Misch wrote:
> > On Fri, Jun 03, 2022 at 11:17:24AM -0700, Nathan Bossart wrote:
> > > 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.
> > 
> > That would not surprise me.  Do you have what you need to continue?
> 
> I'll use that window on Sunday to review what you have.  If you have work in
> progress, please get it to the mailing list by then.

I have the patch mostly done.  I will send something late on Wednesday.



Commits

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