| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Backpatching injection point core facilities to REL_17_STABLE |
| Date: | 2025-08-08 01:34:05 |
| Message-ID: | 1756481.1754616845@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> It is v18 and HEAD are on par in terms of features, with only
> 4eca711bc991 and 7b2eb72b1b8c requiring a cherry-pick, so perhaps we
> should begin with that, before moving with more cherry-picks down to
> v17 as the second step?
> Any thoughts from others? Would it be useful to get that down to the
> back-branches?
I don't have a strong opinion about whether this is worth getting into
the back branches. I do have a strong opinion that just before a
release freeze is not the time to be pushing such changes into stable
branches. Even after the release, I wouldn't touch v13: we have
learned repeatedly that inessential changes made in a branch's final
release are often sources of regret.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-08-08 01:37:46 | Re: Backpatching injection point core facilities to REL_17_STABLE |
| Previous Message | Tom Lane | 2025-08-08 01:29:18 | Identifying function-lookup failures due to argument name mismatches |