From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Update time zone data files to tzdata release 2024b.
In-reply-to: <55A5E01C-1B0F-40F9-94EA-FEDED1575C92@dunslane.net>
References: <362289.1730241666@sss.pgh.pa.us>
 <55A5E01C-1B0F-40F9-94EA-FEDED1575C92@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Tue, 29 Oct 2024 18:06:19 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <595310.1730300440.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 30 Oct 2024 11:00:40 -0400
Message-ID: <595311.1730300440@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/595311.1730300440%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> On Oct 29, 2024, at 5:41 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I would expect that the upgrade tests would pass now for upgrades
>> from v12 or later, thanks to b8ea0f675 et al, but I'm not real
>> sure what to do about testing the out-of-support branches.  Should
>> we back-patch b8ea0f675 as far down as 9.2?

> Or fix/remove the problem rows in AdjustUpgrade.pm I guess

I went to try to test this locally, and got nowhere, because:

	old cluster does not use data checksums but the new one does
	Failure, exiting

What have you done to get around that on crake?

			regards, tom lane