From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: .ready and .done files considered harmful |
Date: | 2024-11-14 00:35:18 |
Message-ID: | ZzVFxi5XmSjLPbfO@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 13, 2024 at 02:52:31PM -0500, Robert Haas wrote:
> On Wed, Nov 13, 2024 at 11:05 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> So, my question now is, would there be much opposition to backpatching
>> beb4e9ba1652 + 1fb17b190341 to REL_14_STABLE?
>
> It seems like it's been long enough now that if the new logic had
> major problems we probably would have found them by now; so I feel
> like it's probably pretty safe. Perhaps it's questionable how many
> people we'll help by back-patching this into one additional release,
> but if you feel it's worth it I wouldn't be inclined to argue.
+1 for v14 as this version is still around for two years.
Even getting that down to v13 would be OK for me at this stage, as,
assuming that something is messed up for a reason or another, we would
still have one year to address any issue that could pop up on
REL_13_STABLE.
Now, the conflicts that exist between v14 and v13 in pgarch.[c|h] are
really risky due to the design changes done in d75288fb27b8, so it is
much better to leave v13 out of scope..
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-11-14 00:48:12 | Re: Fix for pageinspect bug in PG 17 |
Previous Message | Michael Paquier | 2024-11-14 00:27:06 | Re: define pg_structiszero(addr, s, r) |