Re: PITR, checkpoint, and local relations - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject Re: PITR, checkpoint, and local relations
Date
Msg-id 3705826352029646A3E91C53F7189E325185DE@sectorbase2.sectorbase.com
Whole thread Raw
In response to PITR, checkpoint, and local relations  ("J. R. Nield" <jrnield@usol.com>)
Responses Re: PITR, checkpoint, and local relations  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PITR, checkpoint, and local relations
Next
From: Tom Lane
Date:
Subject: Planned simplification of catalog index updates