| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Lukas Fittl <lukas(at)fittl(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "heikki(dot)linnakangas" <heikki(dot)linnakangas(at)iki(dot)fi> |
| Subject: | Re: pg_plan_advice |
| Date: | 2026-04-13 16:01:25 |
| Message-ID: | CA+TgmoaEk5nBCHCWa8epb1Fff4BwroLkdYLfqisKk49qdHGVYw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 8, 2026 at 12:18 PM Melanie Plageman
<melanieplageman(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-04-13 16:06:56 | Re: test_compression, test module for low-level compression APIs (for 2b5ba2a0a141) |
| Previous Message | David Geier | 2026-04-13 15:22:10 | Re: Reduce build times of pg_trgm GIN indexes |