Re: pg_upgrade --logfile option documentation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade --logfile option documentation
Date
Msg-id 11176.1331219945@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade --logfile option documentation  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade --logfile option documentation  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Thu, Mar 08, 2012 at 08:34:53AM -0500, A.M. wrote:
>> It looks like the patch will overwrite the logs in the current working
>> directory, for example, if pg_upgrade is run twice in the same place. Is
>> that intentional? I had imagined that the logs would have been dumped in

> Yes.  I was afraid that continually appending to a log file on every run
> would be too confusing.  I could do only appends, or number the log
> files, that those seemed confusing.

Use one (set of) files, and always append, but at the beginning of each
run print "\npg_upgrade starting at [timestamp]\n\n".  Should make it
reasonably clear, while not losing information.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings
Next
From: Noah Misch
Date:
Subject: Re: sortsupport for text