Re: Hard link backup strategy

On Donnerstag 26 März 2009 Kevin Grittner wrote:
> (1)  Our archive script copies WAL files to a directory on the
> database server, using cp to a one directory followed by mv to
> another (to prevent partial files from being processed).

What "partial files" do you speak about? I'd like to know, as we soon
start doing WAL copies.

> rsync

Incredible. You mean you make the hard link both on client and server,
and afterwards transfer with rsync? That only works for postgresql
<8.3, right? As I understand, 8.3 will reuse the space from updated
tuples and therefore lots of changes in-between will be done.

Or do you use "cluster" to sort the data before copying? But then if one
older record is deleted, all further data will have to be transfered
anyway.

I'm just wondering where the savings come from.

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4