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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2008-10-15 11:59:49 | Opptimizing projections containing unused columns |
Previous Message | Vladimir Dzhuvinov | 2008-10-15 11:09:39 | Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Voras | 2008-10-15 13:21:12 | Re: Backup strategies |
Previous Message | Ivan Voras | 2008-10-15 10:31:08 | Re: Backup strategies |