| From: | Ivan Voras <ivoras(at)freebsd(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Backup strategies |
| Date: | 2008-10-15 13:21:12 |
| Message-ID: | gd4qo2$gvl$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Wakeling | 2008-10-15 13:37:40 | Re: Backup strategies |
| Previous Message | Andrus | 2008-10-15 11:59:49 | Opptimizing projections containing unused columns |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Wakeling | 2008-10-15 13:37:40 | Re: Backup strategies |
| Previous Message | Guillaume Lelarge | 2008-10-15 11:40:30 | Re: Backup strategies |