From: Ivan Voras <ivoras@freebsd.org>
To: pgsql-performance@postgresql.org
Subject: Re: Backup strategies
Date: Wed, 15 Oct 2008 15:21:12 +0200
Message-ID: <gd4qo2$gvl$1@ger.gmane.org> (raw)
In-Reply-To: <48F5D6AE.3000601@lelarge.info>
References: <48F4D693.9000304@lerner.co.il>
<gd4d7q$3ed$1@ger.gmane.org>
<48F5BBFC.80404@krogh.cc>
<gd4gp6$f4p$1@ger.gmane.org>
<48F5D6AE.3000601@lelarge.info>
Guillaume Lelarge wrote:
> Ivan Voras a écrit :
>> It looks like PostgreSQL freezes the state of the "data" directory in
>> this case (and new data goes only to the transaction log - pg_xlog),
>> which effectively creates an application-level snapshot. Good to know.
>
> Nope. Even files in data directory change. That's why the documentation
> warns against tools that emit errors for files that change during the copy.
Ok, thanks. This is a bit off-topic, but if it's not how I imagine it,
then how is it implemented?
Attachments:
signature.asc (application/pgp-signature, 251B) 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-performance@postgresql.org
Cc: ivoras@freebsd.org
Subject: Re: Backup strategies
In-Reply-To: <gd4qo2$gvl$1@ger.gmane.org>
* 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