From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'richt(at)multera(dot)com'" <richt(at)multera(dot)com>, "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PITR, checkpoint, and local relations |
Date: | 2002-08-02 23:50:31 |
Message-ID: | 3705826352029646A3E91C53F7189E325185DB@sectorbase2.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> So I think what will work then is pg_copy (hot backup) would:
> 1) Issue an ALTER SYSTEM BEGIN BACKUP command which turns on
> atomic write,
> checkpoints the database and disables further checkpoints (so
> wal files
> won't be reused) until the backup is complete.
> 2) Change ALTER SYSTEM BACKUP DATABASE TO <directory> read
> the database
> directory to find which files it should backup rather than
> pg_class and for
> each file just use system(cp...) to copy it to the backup directory.
Did you consider saving backup on the client host (ie from where
pg_copy started)?
> 3) ALTER SYSTEM FINISH BACKUP does at it does now and backs
> up the pg_xlog
> directory and renables database checkpointing.
Well, wouldn't be single command ALTER SYSTEM BACKUP enough?
What's the point to have 3 commands?
(If all of this is already discussed then sorry - I'm not going
to start new discussion).
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2002-08-03 00:00:25 | Re: PITR, checkpoint, and local relations |
Previous Message | Tom Lane | 2002-08-02 23:49:07 | Re: PITR, checkpoint, and local relations |