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

From Mikheev, Vadim
Subject Re: PITR, checkpoint, and local relations
Date
Msg-id 3705826352029646A3E91C53F7189E325185DC@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
> I really dislike the notion of turning off checkpointing.  What if the
> backup process dies or gets stuck (eg, it's waiting for some 
> operator to
> change a tape, but the operator has gone to lunch)?  IMHO, backup
> systems that depend on breaking the system's normal 
> operational behavior
> are broken.  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.
That's why I asked are 3 commands from pg_copy required and couldn't
be backup accomplished by issuing single command

ALTER SYSTEM BACKUP <dir | stdout (to copy data to client side)>

(even from pgsql) so backup process would die with entire system -:)
As for tape changing, maybe we could use some timeout and then just
stop backup process.

Vadim


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: Re: PITR, checkpoint, and local relations
Next
From: Tom Lane
Date:
Subject: Re: PITR, checkpoint, and local relations