From: Simon Riggs <simon@2ndQuadrant.com>
To: Ivan Voras <ivoras@freebsd.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Backup strategies
Date: Fri, 17 Oct 2008 20:35:41 +0100
Message-ID: <1224272141.3808.437.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <gd4tad$qlg$1@ger.gmane.org>
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>
<gd4qo2$gvl$1@ger.gmane.org>
<alpine.DEB.1.10.0810151432280.15851@aragorn.flymine.org>
<gd4tad$qlg$1@ger.gmane.org>
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
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: simon@2ndQuadrant.com, ivoras@freebsd.org
Subject: Re: Backup strategies
In-Reply-To: <1224272141.3808.437.camel@ebony.2ndQuadrant>
* 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