Re: pg_upgrade should truncate/remove its logs before running - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_upgrade should truncate/remove its logs before running
Date
Msg-id 0623B782-3EDE-415D-9D86-7F495D23CCB6@dunslane.net
Whole thread Raw
In response to Re: pg_upgrade should truncate/remove its logs before running  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> On Feb 6, 2022, at 7:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Michael Paquier <michael@paquier.xyz> writes:
>>> On Sun, Feb 06, 2022 at 08:32:59AM -0500, Andrew Dunstan wrote:
>>> But the commit really shouldn't have happened until we know that most
>>> buildfarm owners have installed it. It should have waited wait not just
>>> for the release but for widespread deployment. Otherwise we will just
>>> lose any logging for an error that might appear.
>
>> Would it be better if I just revert the change for now then and do it
>> again in one/two weeks?
>
> I don't see a need to revert it.
>
> I note, though, that there's still not been any email to the buildfarm
> owners list about this update.
>
>

It’s stuck in moderation

Cheers

Andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade should truncate/remove its logs before running
Next
From: "Jonathan S. Katz"
Date:
Subject: 2022-02-10 release announcement draft