From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: Hard link backup strategy
Date: Fri, 27 Mar 2009 08:43:40 +0100
Message-ID: <200903270843.45051@zmi.at> (raw)
In-Reply-To: <49CBA19F.EE98.0025.0@wicourts.gov>
References: <49CB9D8302000025000257DF@gwmta.wicourts.gov>
<49CBA19F02000025000257EB@gwmta.wicourts.gov>
<49CBA19F.EE98.0025.0@wicourts.gov>
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
Attachments:
signature.asc (application/pgp-signature, 196B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: michael.monnerie@is.it-management.at
Subject: Re: Hard link backup strategy
In-Reply-To: <200903270843.45051@zmi.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox