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

From Tom Lane
Subject Re: pg_upgrade should truncate/remove its logs before running
Date
Msg-id 803503.1644194379@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade should truncate/remove its logs before running  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_upgrade should truncate/remove its logs before running
Re: pg_upgrade should truncate/remove its logs before running
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: GSoC 2022
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_upgrade should truncate/remove its logs before running