Re: pg_upgrade --logfile option documentation

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade --logfile option documentation
Date: 2012-03-08 21:37:53
Message-ID: 1331242673.1197.13.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On tor, 2012-03-08 at 10:06 -0500, A.M. wrote:
> > 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?

I don't want to see some tool unconditionally writing files (log or
otherwise) with unpredictable names. That would make it impossible to
clean up in a wrapper script.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message A.M. 2012-03-08 21:44:55 Re: pg_upgrade --logfile option documentation
Previous Message David E. Wheeler 2012-03-08 21:33:24 Re: regress bug