Re: Backpatching injection point core facilities to REL_17_STABLE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Backpatching injection point core facilities to REL_17_STABLE
Date
Msg-id 1756481.1754616845@sss.pgh.pa.us
Whole thread Raw
In response to Re: Backpatching injection point core facilities to REL_17_STABLE  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Backpatching injection point core facilities to REL_17_STABLE
List pgsql-hackers
Michael Paquier <michael@paquier.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Identifying function-lookup failures due to argument name mismatches
Next
From: Michael Paquier
Date:
Subject: Re: Backpatching injection point core facilities to REL_17_STABLE