> On Dec 7, 2021, at 8:33 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> However, it wouldn't be a great idea to back-patch a
> completely arbitrary subset of our fixes into those branches, because
> then it sort of gets confusing to understand what the status of that
> branch is. I don't know that I'm terribly bothered by the idea that
> the behavior of the branch might deviate from the last official
> release, because most bug fixes are pretty minor and wouldn't really
> affect testing much, but it would be a little annoying to explain to
> users that those branches contain an arbitrary subset of newer fixes,
> and a little hard for us to understand what is and is not there.
Wouldn't you be able to see what changed by comparing the last released tag for version X.Y against the RELX_Y_STABLE
branch? Something like `git diff REL8_4_22 origin/REL8_4_STABLE > buildability.patch`?
Having such a patch should make reproducing old corruption bugs easier, as you could apply the buildability.patch to
thelast branch that contained the bug. If anybody did that work, would we want it committed somewhere?
REL8_4_19_BUILDABLEor such? For patches that apply trivially, that might not be worth keeping, but if the merge is
difficult,maybe sharing with the community would make sense.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company