From: Ivan Voras <ivoras@freebsd.org>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Backup strategies
Date: Wed, 15 Oct 2008 16:58:46 +0200
Message-ID: <9bbcef730810150758i4cc25431g41e4805c024615fd@mail.gmail.com> (raw)
In-Reply-To: <20081015141327.GW16893@yugib.highrise.ca>
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>
<20081015141327.GW16893@yugib.highrise.ca>
2008/10/15 Aidan Van Dyk <aidan@highrise.ca>:
> * Ivan Voras <ivoras@freebsd.org> [081015 10:05]:
>
>> 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? Why
>> not run with pg_start_backup() always enabled?
>
> I think your missing the whole point of "pg_start_backup()".
> pg_start_backup()" is *part* of a full PITR/backup run. i.e. you use it
> when you have an archive command working as well. It's *not* mean tto
> just allow you to do a filesystem copy inside a running data directory.
Possibly - that's why I'm sticking to this thread :) My context is
doing full filesystem-only copies/backups of the database (xlogs &
all) - is pg_start_backup() applicable?
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: ivoras@freebsd.org, aidan@highrise.ca
Subject: Re: Backup strategies
In-Reply-To: <9bbcef730810150758i4cc25431g41e4805c024615fd@mail.gmail.com>
* 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