pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas F. O'Connell <tfo@sitening.com>
To: PgSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Continuous On-line Backups
Date: Sat, 25 Mar 2006 00:23:22 -0600
Message-ID: <35415ACA-B193-4040-B032-7746E2DF3510@sitening.com> (raw)
In-Reply-To: <200603250019.53577.peter_e@gmx.net>
References: <33C7314B-CE32-4E5A-8D73-1AA0B32EBB84@sitening.com>
	<200603250019.53577.peter_e@gmx.net>


On Mar 24, 2006, at 5:19 PM, Peter Eisentraut wrote:

> Thomas F. O'Connell wrote:
>> So long as I know that nothing will access the recovery database with
>> write activity, is there a way to toggle the continuity so that I
>> could allow recovery to complete on a nightly basis, pg_dump the
>> recovered database (a read-only action), and then resume recovering?
>
> Even a read-only action uses up transaction numbers and other  
> things, so
> I'd expect that to be a problem.

Good point.

My chief concern with the loss of flexibility would be the greater  
difficulty in detecting a lost or corrupted WAL segment file if  
archive_command is operating across a network (or locally, with an  
external script responsible for moving the files across the network).

With nightly pg_dumps/pg_restores, at least I know my window of a  
valid database is on the order of 24 hours.

Simon Riggs recently recommended base backups as a weekly process  
with a continuous on-line backup operating in the interim. I guess  
the price to be paid for the higher availability is increased  
scrutiny of the process.

--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC

http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)



view thread (3+ messages)

Message-ID: <35415ACA-B193-4040-B032-7746E2DF3510@sitening.com>
Permalink:  ../35415ACA-B193-4040-B032-7746E2DF3510@sitening.com/
Also on:    postgresql.org/message-id/35415ACA-B193-4040-B032-7746E2DF3510@sitening.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tfo@sitening.com
  Subject: Re: Continuous On-line Backups
  In-Reply-To: <35415ACA-B193-4040-B032-7746E2DF3510@sitening.com>
  References: <33C7314B-CE32-4E5A-8D73-1AA0B32EBB84@sitening.com> <200603250019.53577.peter_e@gmx.net> <35415ACA-B193-4040-B032-7746E2DF3510@sitening.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