Re: Extension pg_trgm, permissions and pg_dump order - Mailing list pgsql-bugs

From Noah Misch
Subject Re: Extension pg_trgm, permissions and pg_dump order
Date
Msg-id 20220613034551.GB3728437@rfd.leadboat.com
Whole thread Raw
In response to Re: Extension pg_trgm, permissions and pg_dump order  (Noah Misch <noah@leadboat.com>)
Responses Re: Extension pg_trgm, permissions and pg_dump order  (Nathan Bossart <nathandbossart@gmail.com>)
Re: Extension pg_trgm, permissions and pg_dump order  (Noah Misch <noah@leadboat.com>)
List pgsql-bugs
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.



pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Unable to make use of "deep" JSONB index
Next
From: Michael Paquier
Date:
Subject: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error