From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Cleaning up nbtree after logical decoding on standby work |
Date: | 2023-05-29 00:31:02 |
Message-ID: | ZHPyRiSOk7DxRBdD@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 26, 2023 at 04:48:37PM -0700, Peter Geoghegan wrote:
> I'd have thought the subject line "Cleaning up nbtree after logical
> decoding on standby work" made it quite clear that this patch was
> targeting 16.
Hmm, okay. I was understanding that as something for v17, honestly.
> It's not refactoring work -- not really. The whole idea of outright
> removing the use of P_NEW in nbtree was where I landed with this after
> a couple of hours of work. In fact I almost posted a version without
> that, though that was worse in every way to my final approach.
>
> I first voiced concerns about this whole area way back on April 4,
> which is only 3 days after commit 61b313e4 went in:
>
> https://postgr.es/m/CAH2-Wz=jGryxWm74G1khSt0zNPUNhezYJnvSjNo2t3Jswtb8ww@mail.gmail.com
Sure. My take is that if this patch were to be sent at the beginning
of April, it could have been considered in v16. However, deciding
such a matter at the end of May after beta1 has been released is a
different call. You may want to make sure that the RMT is OK with
that, at the end.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Shinoda, Noriyoshi (PN Japan FSIP) | 2023-05-29 00:39:08 | [16Beta1][doc] Add BackendType for standalone backends |
Previous Message | David Rowley | 2023-05-28 21:42:05 | Re: benchmark results comparing versions 15.2 and 16 |