Skip site navigation (1) Skip section navigation (2)

Re: Hard link backup strategy

From: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Hard link backup strategy
Date: 2009-03-27 07:43:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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 

I'm just wondering where the savings come from.

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

In response to


pgsql-admin by date

Next:From: Tony WebbDate: 2009-03-27 09:20:19
Subject: Re: pg_ctlcluster not logging error (memory problem likely)
Previous:From: Tom LaneDate: 2009-03-26 22:35:35
Subject: Re: pg_ctlcluster not logging error (memory problem likely)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group