From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Fixes required for cross version update testing |
Date: | 2023-01-13 22:20:41 |
Message-ID: | ca55c6c3-50d1-172c-05ee-a3fcf6f1c113@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Over at [1] there was some discussion of moving knowledge of what's
required to be fixed from old branch repos to be able to upgrade them
into the core code, instead of having it reside in a buildfarm client
module.
Here's a piece of WIP for that, in the form of a perl module that
provides a function that takes an old version number / tag and provides
the set of sql statements that need to be run to make the old repo
upgradeable. It still needs a good deal of polish, but it's a start.
The advantage is that it makes it far less likely that the buildfarm
maintainer (i.e. me for now) is a bottleneck in fixing issues that arise
from development. This is by far the biggest area where we have seen
buildfarm breakage for cross version upgrade testing.
cheers
andrew
[1] https://postgr.es/m/951602.1673535249@sss.pgh.pa.us
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
AdjustUpgrade.pm | application/x-perl | 3.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Cary Huang | 2023-01-13 22:22:58 | Re: Patch: Global Unique Index |
Previous Message | Andres Freund | 2023-01-13 21:59:56 | Re: Decoupling antiwraparound autovacuum from special rules around auto cancellation |