| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Ivan Voras <ivoras(at)freebsd(dot)org> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Backup strategies |
| Date: | 2008-10-17 19:35:41 |
| Message-ID: | 1224272141.3808.437.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Wed, 2008-10-15 at 16:05 +0200, Ivan Voras wrote:
> So, pg_start_backup() freezes the data at the time it's called but
> still
> data and xlog are changed, in a different way that's safe to backup?
No, that's not how it works. The pg_start_backup() records the point
that we must rollforward from. There is no freezing.
> Why
> not run with pg_start_backup() always enabled?
It's not a mode that can be enabled/disabled. Its a starting point.
You should run pg_start_backup() each time you run a backup, just like
the fine manual describes.
Check your backups...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2008-10-17 19:43:08 | Re: Annoying Reply-To |
| Previous Message | Diogo Biazus | 2008-10-17 19:32:23 | Re: Copying Blobs between two tables using Insert stmt |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2008-10-17 19:43:08 | Re: Annoying Reply-To |
| Previous Message | Serge Fonville | 2008-10-17 19:26:27 | Re: Annoying Reply-To |