Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 0035B9FA376 for ; Mon, 30 Oct 2006 06:53:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 15116-06 for ; Mon, 30 Oct 2006 10:53:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 5F00A9FA0FF for ; Mon, 30 Oct 2006 06:53:37 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id 30so946092ugc for ; Mon, 30 Oct 2006 02:53:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=T8hhgQ8VP44faxgp7hXDPnE+NylC9y0UFdTLON4mEI2P8MHjjegr2NrsB1aVu9czTwQJwu03SjfR2W5ZrR+XG0RbtKYFEqAR0TLEENPyW2aRmsRnguzteI6rRCoLPZORTu972ORGpCq0tTNgij1GP0bHy1RXgT902TM7Ncmoz7U= Received: by 10.67.97.18 with SMTP id z18mr3860928ugl; Mon, 30 Oct 2006 02:53:35 -0800 (PST) Received: by 10.67.26.19 with HTTP; Mon, 30 Oct 2006 02:53:35 -0800 (PST) Message-ID: <82e1a9bd0610300253y1c999f31k5ba6ac086bcfb802@mail.gmail.com> Date: Mon, 30 Oct 2006 16:23:35 +0530 From: "Moiz Kothari" To: "Shoaib Mir" Subject: Re: 100% failover + replication solution Cc: "Ben Suffolk" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_92690_2731456.1162205615394" References: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com> <7CA68A94-ED1E-49C9-ACF2-2A34936333DC@vanilla.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/205 X-Sequence-Number: 23508 ------=_Part_92690_2731456.1162205615394 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Shoaib, It sure does, i saw PGCLUSTER, but 3 reasons for having a postgres specific solution. 1) If pgcluster stops further development, it would be lot more hassel when upgrading to a different version of postgres. 2) Postgres specific solution would help alot going ahead in future. 3) Also architecture of pgcluster might make things slower as it updates complete cluster before confirming the request. There are lots of them available in market, but i think WAL solution should be available, if not then the thought process should be there going ahead. I am expecting a solution out of WAL logs. Let me know if you have any thoughts about it. Regards, Moiz Kothari On 10/30/06, Shoaib Mir wrote: > > There is this project which actually is not released yet, but something > that you want to achieve :) > > http://pgfoundry.org/projects/pgpitrha > > Regards, > ------- > Shoaib Mir > EnterpriseDB (www.enterprisedb.com) > > On 10/30/06, Ben Suffolk < ben@vanilla.net> wrote: > > > > Guys, > > > > > > I have been thinking about this and wanted to see if it can be > > > achived. I wanted to make a 100% failover solution for my postgres > > > databases. The first thing that comes to my mind is doing it using > > > WAL logs. Am attaching the diagram for which i will write more here. > > > > While its not the solution you were looking at, have you seen > > PGCluser :- > > > > http://pgcluster.projects.postgresql.org/index.html > > > > I have not tried it, but was looking the other week at various fail- > > over type solutions and came across it. It seems to be able to do > > what you want. > > > > Ben > > > > > > > > > > > > > > ---------------------------(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 > > > > ------=_Part_92690_2731456.1162205615394 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Shoaib,

It sure does, i saw PGCLUSTER, but 3 reasons for having a postgres specific solution.

1) If pgcluster stops further development, it would be lot more hassel when upgrading to a different version of postgres.
2) Postgres specific solution would help alot going ahead in future.
3) Also architecture of pgcluster might make things slower as it updates complete cluster before confirming the request.

There are lots of them available in market, but i think WAL solution should be available, if not then the thought process should be there going ahead. I am expecting a solution out of WAL logs. Let me know if you have any thoughts about it.

Regards,
Moiz Kothari

On 10/30/06, Shoaib Mir <shoaibmir@gmail.com> wrote:
There is this project which actually is not released yet, but something that you want to achieve :)

http://pgfoundry.org/projects/pgpitrha

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

On 10/30/06, Ben Suffolk < ben@vanilla.net> wrote:
> Guys,
>
> I have been thinking about this and wanted to see if it can be
> achived. I wanted to make a 100% failover solution for my postgres
> databases. The first thing that comes to my mind is doing it using
> WAL logs. Am attaching the diagram for which i will write more here.

While its not the solution you were looking at, have you seen
PGCluser :-

http://pgcluster.projects.postgresql.org/index.html

I have not tried it, but was looking the other week at various fail-
over type solutions and came across it. It seems to be able to do
what you want.

Ben






---------------------------(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


------=_Part_92690_2731456.1162205615394--