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 4706d955-8bfb-d9e5-707c-d93a027621e3@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 2/6/22 19:39, Tom Lane 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.
>
>             


The announcement was held up in list moderation for 20 hours or so.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Documentation about PL transforms
Next
From: "David G. Johnston"
Date:
Subject: Re: Storage for multiple variable-length attributes in a single row