From: Shoaib Mir <shoaibmir@gmail.com>
To: Moiz Kothari <moizpostgres@gmail.com>
Cc: Ben Suffolk <ben@vanilla.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: 100% failover + replication solution
Date: Mon, 30 Oct 2006 17:49:04 +0500
Message-ID: <bf54be870610300449uc1aa708mf4cecb7c3fe16ecc@mail.gmail.com> (raw)
In-Reply-To: <82e1a9bd0610300253y1c999f31k5ba6ac086bcfb802@mail.gmail.com>
References: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com>
<7CA68A94-ED1E-49C9-ACF2-2A34936333DC@vanilla.net>
<bf54be870610300223u1a2d78b5j47525531bd5ce0a0@mail.gmail.com>
<82e1a9bd0610300253y1c999f31k5ba6ac086bcfb802@mail.gmail.com>
Hi Moiz,
If I had to choose for your case where you want to direct your selects to
slave node and inserts/updates on master, I would have opted for Slony or
PGCluster.
Using PITR for HA can be a good option if you want to switch between primary
and secondary server, where you can store the archive files on a shared disk
and place a recovery file with in $PGDATA and automate the process where it
can run the process of recovery on each primary and seconday like for
example 5 times a day as it all depends on the number of transactions
happening on the db server. I have seen a few users doing this for routine
VACUUM FULL process as a maintanence activity.
Thanks,
---------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 10/30/06, Moiz Kothari <moizpostgres@gmail.com> wrote:
>
> 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
> > >
> >
> >
>
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, moizpostgres@gmail.com, ben@vanilla.net
Subject: Re: 100% failover + replication solution
In-Reply-To: <bf54be870610300449uc1aa708mf4cecb7c3fe16ecc@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>
* 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