Request a Demo
Home   >   mailing lists

Re: pg_plan_advice - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_plan_advice
Date
Msg-id CA+TgmoaEk5nBCHCWa8epb1Fff4BwroLkdYLfqisKk49qdHGVYw@mail.gmail.com
Whole thread
In response to Re: pg_plan_advice  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: pg_plan_advice
List pgsql-hackers
Tree view 
On Wed, Apr 8, 2026 at 12:18 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> > > No strong opinion about that.  Certainly waiting a couple of weeks
> > > to gather more data seems reasonable.
> >
> > I am only 1/3 of the RMT, but I am fine with the plan as stated.
>
> I agree with waiting a few weeks to continue catching bugs.

Sounds like we have a consensus. I have committed the three bug-fix
patches (unrelated to the retry-loop stuff) plus the preparatory
refactoring patch for the retry-loop patch. That renames a few
identifiers, so it seemed best to get it out of the way sooner rather
than later. I'll hold off on the main retry-loop patch for now. So far
I haven't seen any other buildfarm failures that look related to this
issue, so either I've missed some (which is certainly possible) or the
chances of failure are very low.

Thanks,

--
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: David Geier
Date:
Subject: Re: Reduce build times of pg_trgm GIN indexes
Next
From: Jacob Champion
Date:
Subject: Re: test_compression, test module for low-level compression APIs (for 2b5ba2a0a141)