Re: pg_upgrade --logfile option documentation

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade --logfile option documentation
Date: 2012-03-08 15:06:28
Message-ID: 3B25BC33-EA77-489A-BB25-AB686EABBED8@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2012-03-08 15:11:37 Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings
Previous Message Bruce Momjian 2012-03-08 15:00:25 Re: pg_upgrade --logfile option documentation