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

From A.M.
Subject Re: pg_upgrade --logfile option documentation
Date
Msg-id 3B25BC33-EA77-489A-BB25-AB686EABBED8@themactionfaction.com
Whole thread Raw
In response to Re: pg_upgrade --logfile option documentation  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade --logfile option documentation  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Mar 8, 2012, at 10:00 AM, Bruce Momjian wrote:
> 
> 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.
> 
>> the /tmp directory so that one can compare results if the first pg_upgrade
>> run had been errant.
> 
> You would have to copy the file to a new name before re-running
> pg_upgrade.
> 
> The only reason I truncate them on start is that I am appending to them
> in many places in the code, and it was easier to just truncate them on
> start rather than to remember where I first write to them.
> 


mktemps?





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade --logfile option documentation
Next
From: Noah Misch
Date:
Subject: Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings