pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-admin@postgresql.org
Cc: Jeff Larsen <jlar310@gmail.com>
Subject: Re: pg_start_backup without WAL archiving
Date: Sun, 25 Nov 2007 17:04:22 +0100
Message-ID: <200711251704.23628.peter_e@gmx.net> (raw)
In-Reply-To: <d1f9b6f00711250733p25df13e3u4f4d4014654533d3@mail.gmail.com>
References: <200711251524.08249.peter_e@gmx.net>
	<d1f9b6f00711250733p25df13e3u4f4d4014654533d3@mail.gmail.com>

Jeff Larsen wrote:
> On Nov 25, 2007 8:24 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> > Why is it not allowed to call pg_start_backup when WAL archiving is off?
> > Wouldn't this be useful as a discrete file system backup without PITR
> > capability?
>
> Because a file system level backup is no good unless the database is
> stopped, or you are using PITR.

You are begging the question.  If I enable WAL archiving, make a base backup 
to a safe place, and my data center goes up in flame immediately afterwards 
without a WAL segment being archived, that base backup should still be 
usable.  Or maybe not.  That's the question.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/



view thread (5+ messages)  latest in thread

Message-ID: <200711251704.23628.peter_e@gmx.net>
Permalink:  ../200711251704.23628.peter_e@gmx.net/
Also on:    postgresql.org/message-id/200711251704.23628.peter_e@gmx.net

 · 

reply

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-admin@postgresql.org
  Cc: peter_e@gmx.net, jlar310@gmail.com
  Subject: Re: pg_start_backup without WAL archiving
  In-Reply-To: <200711251704.23628.peter_e@gmx.net>

* 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