pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas F. O'Connell <tfo@sitening.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: andy.shellam@mailnetwork.co.uk
Cc: pgsql-admin@postgresql.org
Subject: Re: PITR as Online Backup Solution
Date: Fri, 3 Mar 2006 12:10:00 -0600
Message-ID: <F398D440-FACE-4991-AF97-0FA104CA2D04@sitening.com> (raw)
In-Reply-To: <1141408830.27729.512.camel@localhost.localdomain>
References: <!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABOiYOz9rZ9SIlOq0NqO/h8AQAAAAA=@mailnetwork.co.uk>
	<1141408830.27729.512.camel@localhost.localdomain>


On Mar 3, 2006, at 12:00 PM, Simon Riggs wrote:

> On Fri, 2006-03-03 at 10:23 +0000, Andy Shellam wrote:
>
>> Then you would have to find a method of telling the script
>> that you wish to bring the database up and it will exit and allow  
>> PGSQL to
>> come up at the current state with the latest data.
>
>> Replication sounds like a better option
>
> If you want auto failover, then you will need a package that detects
> that accurately and can initiate any required actions, whatever method
> you choose of keeping multiple systems in sync.
>
> IMHO auto failover needs *extensive* testing and failure analysis to
> make it more robust and practically useful than manual failover, so is
> not quite the magic bullet it may appear.
>
> Best Regards, Simon Riggs

Auto failover is not a requirement for me. My primary goals are to  
reduce the need for pg_dump to occur nightly against a large  
production database and to reduce the window of potential data loss  
in a failover scenario, where the assumption is that the failover  
would be managed manually.

There's too much application-inspired DDL and too many tables (as a  
result of an inheritance-heavy) data model for Slony to be a viable  
solution in the short term.

--
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 (11+ messages)  latest in thread

Message-ID: <F398D440-FACE-4991-AF97-0FA104CA2D04@sitening.com>
Permalink:  ../F398D440-FACE-4991-AF97-0FA104CA2D04@sitening.com/
Also on:    postgresql.org/message-id/F398D440-FACE-4991-AF97-0FA104CA2D04@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, simon@2ndquadrant.com, andy.shellam@mailnetwork.co.uk
  Subject: Re: PITR as Online Backup Solution
  In-Reply-To: <F398D440-FACE-4991-AF97-0FA104CA2D04@sitening.com>
  References: <!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABOiYOz9rZ9SIlOq0NqO/h8AQAAAAA=@mailnetwork.co.uk> <1141408830.27729.512.camel@localhost.localdomain> <F398D440-FACE-4991-AF97-0FA104CA2D04@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