[Pkg-postgresql-public] pg_upgrade support in pg_upgradecluster

Christoph Berg myon at debian.org
Thu Jul 26 07:16:48 UTC 2012


Re: Martin Pitt 2012-07-25 <20120725161023.GL3264 at piware.de>
> > Come to think of it, I like putting it into /var/log/postgresql and just
> > leaving it there, as a kind of log output.  Because there could be
> > things in there that you might want to look at even if successful.
> > 
> > But in terms of predictable file names, what do you suggest to do if
> > someone runs the same upgrade several times, e.g., after failed
> > attempts?
> 
> I wouldn't consider them that precious; as the new cluster is either
> automatically deleted (on failure) or manually deleted before
> re-upgrading (if you aren't satisfied), there is little point in
> keeping old upgrade logs around IMHO. If you think there is, I'd
> rather append a date/time suffix than a nonce.

Just append to the file instead of truncating it?

Christoph
-- 
cb at df7cb.de | http://www.df7cb.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20120726/e6afc905/attachment.pgp>


More information about the Pkg-postgresql-public mailing list