Re: PITR, checkpoint, and local relations

Vadim Mikheev <vmikheev@sectorbase.com>

From: "Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: richt@multera.com, "J. R. Nield" <jrnield@usol.com>, Bruce Momjian <pgman@candle.pha.pa.us>, PostgreSQL Hacker <pgsql-hackers@postgresql.org>
Date: 2002-08-03T00:31:04Z
Lists: pgsql-hackers
> >> It should be sufficient to force a checkpoint when you
> >> start and when you're done --- altering normal operation 
> in between is
> >> a bad design.
> 
> > But you have to prevent log files reusing while you copy data files.
> 
> No, I don't think so.  If you are using PITR then you presumably have
> some process responsible for archiving off log files on a continuous
> basis.  The backup process should leave that normal 
> operational behavior in place, not muck with it.

Well, PITR without log archiving could be alternative to
pg_dump/pg_restore, but I agreed that it's not the big
feature to worry about.

Vadim