Re: pgsql: Update time zone data files to tzdata release 2024b.
| От | Andrew Dunstan |
|---|---|
| Тема | Re: pgsql: Update time zone data files to tzdata release 2024b. |
| Дата | |
| Msg-id | CAD5tBcLHz6NLCW_65qYka08HRVeT6w15Cd1YFKmHV5Ou43Fu4g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pgsql: Update time zone data files to tzdata release 2024b. (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: pgsql: Update time zone data files to tzdata release 2024b.
|
| Список | pgsql-committers |
On Wed, Oct 30, 2024 at 11:00 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
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?
I did this:
I was intending to push a new client release with it but things got kinda screwy the last 10 days. I will try to push it out later this week.
Meanwhile I think you should see the same result without this issue if you test using v17 or earlier instead of master.
cheers
andrew
В списке pgsql-committers по дате отправления: