pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shoaib Mir <shoaibmir@gmail.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: 100% failover + replication solution
Date: Mon, 30 Oct 2006 19:29:11 +0500
Message-ID: <bf54be870610300629w4ebcecb0p435e729995677841@mail.gmail.com> (raw)
In-Reply-To: <20061030133806.GA16730@phlogiston.dyndns.org>
References: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com>
	<7CA68A94-ED1E-49C9-ACF2-2A34936333DC@vanilla.net>
	<bf54be870610300223u1a2d78b5j47525531bd5ce0a0@mail.gmail.com>
	<82e1a9bd0610300253y1c999f31k5ba6ac086bcfb802@mail.gmail.com>
	<bf54be870610300449uc1aa708mf4cecb7c3fe16ecc@mail.gmail.com>
	<82e1a9bd0610300511u35a3e156u22b3c600c69edd24@mail.gmail.com>
	<20061030133806.GA16730@phlogiston.dyndns.org>

Hi Moiz,

This might help you :) -->
http://developer.postgresql.org/pgdocs/postgres/warm-standby.html

Thanks,
-------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 10/30/06, Andrew Sullivan <ajs@crankycanuck.ca> wrote:
>
> On Mon, Oct 30, 2006 at 06:41:54PM +0530, Moiz Kothari wrote:
> > I agree that PGCluster might be a better option, i dont want to go with
> > Slony because of primary key constraints.
>
> I don't know what the "primary key constraints" issue you have is,
> but Slony would be inappropriate for a "100% failover" system anyway:
> you can't know you haven't trapped data on the origin.  This is in
> fact true for the WAL shipping you suggested, also.  The only way to
> achieve 100% reliable failover today, with guaranteed no data loss,
> is to use a system that commits all the data on two machines at the
> same time in the same transaction.  I haven't seen any argument so
> far that there is any such system "out of the box", although with two
> phase commit support available, it would seem that some systems could
> be extended in that direction.
>
> The other answer for all of this is to do it with hardware, but
> that's a shared-disk system, so if your disk blows up, you have a
> problem.  Or, if you're using the operating system of people who
> don't know how fsck works.  I don't know anyone who has that problem;
> certainly not any vendors whose name starts with 'I' and ends with
> 'M'.
>
> > 1) It might slow down the process a bit. as confirmation happens after
> > transaction gets comitted to all the nodes.
>
> Anyone who tells you that you can have completely reliable data
> replication with no performance hit is trying to sell you a bridge in
> Brooklyn.  If you want reliable data replication that guarantees you
> can have automatic failover, you are going to pay for it somehow; the
> question is which compromise you want to make.  That seems to be
> something you'll need to decide.
>
> > 2) Its difficult to convince, as it is an external project and if
> support
> > for the same stops or future versions of postgres does not work, it
> might be
> > a problem.
>
> If you have this problem, probably free software isn't for you.
> PostgreSQL is a modular system, and people use different components
> together in deployed systems.  This happens to be true of commercial
> offerings too (if not, you could buy the cheapest version of, say,
> Oracle and get RAC in the bargain), but they _sell_ it to you as
> though it were one big package.  To the extent your managers don't
> understand this, you're always going to have a problem using free
> software.
>
> A
> --
> Andrew Sullivan  | ajs@crankycanuck.ca
> In the future this spectacle of the middle classes shocking the avant-
> garde will probably become the textbook definition of Postmodernism.
>                 --Brad Holland
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
>

view thread (20+ messages)  latest in thread

Message-ID: <bf54be870610300629w4ebcecb0p435e729995677841@mail.gmail.com>
Permalink:  ../bf54be870610300629w4ebcecb0p435e729995677841@mail.gmail.com/
Also on:    postgresql.org/message-id/bf54be870610300629w4ebcecb0p435e729995677841@mail.gmail.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: shoaibmir@gmail.com, ajs@crankycanuck.ca
  Subject: Re: 100% failover + replication solution
  In-Reply-To: <bf54be870610300629w4ebcecb0p435e729995677841@mail.gmail.com>
  References: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com> <7CA68A94-ED1E-49C9-ACF2-2A34936333DC@vanilla.net> <bf54be870610300223u1a2d78b5j47525531bd5ce0a0@mail.gmail.com> <82e1a9bd0610300253y1c999f31k5ba6ac086bcfb802@mail.gmail.com> <bf54be870610300449uc1aa708mf4cecb7c3fe16ecc@mail.gmail.com> <82e1a9bd0610300511u35a3e156u22b3c600c69edd24@mail.gmail.com> <20061030133806.GA16730@phlogiston.dyndns.org> <bf54be870610300629w4ebcecb0p435e729995677841@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