pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Replication - state of the art?
Date: Wed, 1 Mar 2006 18:23:13 -0500
Message-ID: <20060301232313.GA5656@phlogiston.dyndns.org> (raw)
In-Reply-To: <20060301221518.GW82012@pervasive.com>
References: <20060301133041.8EFFA19B797@smtp03l.fasthosts.co.uk>
	<4405DF32.4070307@obviously.com>
	<20060301182803.GK17356@phlogiston.dyndns.org>
	<4405F5C6.1040300@obviously.com>
	<20060301194918.GA5200@phlogiston.dyndns.org>
	<20060301221518.GW82012@pervasive.com>

On Wed, Mar 01, 2006 at 04:15:18PM -0600, Jim C. Nasby wrote:
> You could also use WAL shipping and some PITR trickery to keep a 'warm
> standby' database up to date. How far behind it falls is up to you,
> since you'll be periodically syncing the current WAL file to the backup
> machine. Do the sync once a minute, and at most you lose 60 seconds of
> data.

Right.  But you have to write all of that, and write the failover
scripts, and such like.  And the OP suggested that there wasn't time
budget for that.  But it'd work.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
		--George Orwell



view thread (7+ messages)

Message-ID: <20060301232313.GA5656@phlogiston.dyndns.org>
Permalink:  ../20060301232313.GA5656@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20060301232313.GA5656@phlogiston.dyndns.org

 · 

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-sql@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: Replication - state of the art?
  In-Reply-To: <20060301232313.GA5656@phlogiston.dyndns.org>

* 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