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

Re: Backup strategies

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Ivan Voras <ivoras(at)freebsd(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Backup strategies
Date: 2008-10-15 11:40:30
Message-ID: 48F5D6AE.3000601@lelarge.info (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-performance
Ivan Voras a écrit :
> Jesper Krogh wrote:
>>[...]
>> It worked when I tested it, but I may just have been darn lucky.
> 
> No, it should be ok - I just didn't catch up with the times :) At least
> that's my interpretation of this paragraph in documentation:
> 
> """Some backup tools that you might wish to use emit warnings or errors
> if the files they are trying to copy change while the copy proceeds.
> This situation is normal, and not an error, when taking a base backup of
> an active database; so you need to ensure that you can distinguish
> complaints of this sort from real errors..."""
> 
> 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.


-- 
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com

In response to

Responses

pgsql-performance by date

Next:From: Ivan VorasDate: 2008-10-15 13:21:12
Subject: Re: Backup strategies
Previous:From: Ivan VorasDate: 2008-10-15 10:31:08
Subject: Re: Backup strategies

pgsql-general by date

Next:From: AndrusDate: 2008-10-15 11:59:49
Subject: Opptimizing projections containing unused columns
Previous:From: Vladimir DzhuvinovDate: 2008-10-15 11:09:39
Subject: Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)?

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