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

From Daniel Gustafsson
Subject Re: pg_upgrade should truncate/remove its logs before running
Date
Msg-id E66B93B0-8579-48BC-9CA4-4C6E3A97408D@yesql.se
Whole thread Raw
In response to Re: pg_upgrade should truncate/remove its logs before running  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
> On 16 Dec 2021, at 12:11, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:

> Could we make it write just one log file?  Is having multiple log files better?

Having individual <checkname>.txt files from checks with additional information
on how to handle the error are quite convenient when writing wrappers around
pg_upgrade (speaking from experience of having written multiple pg_upgraade
frontends).  Parsing a single logfile is more work, and will break existing
scripts.

I'm in favor of a predictable by default logpath, with a parameter to override,
as mentioned upthread.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_upgrade should truncate/remove its logs before running
Next
From: Peter Eisentraut
Date:
Subject: Re: Transparent column encryption