From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Improving Availability |
Date: | 2005-12-14 15:46:49 |
Message-ID: | 43A03E69.6040608@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Guido Neitzer wrote:
> Hi.
>
> I have two server boxes (Apple Xserve G5). WebServers and applications
> are installed on both machines, the load is distributed by a
> loadbalancer to both machines.
>
> How can I make a setup in a way that the database is also tolerant
> against failure? What I actually need is a mechanism that keeps both
> machines synchronized.
>
> What is the way to go for this?
It depends on how "failsafe" you want to be.
You could use log-shipping and PITR (see manuals) to make sure machine 2
can be restored to where machine 1 was "recently".
You could use replication (e.g. Slony) To copy transactions from machine
1 to machine 2.
You could use something like pgpool to copy queries to both servers. You
need to make sure you understand the implications of this as regards
timestamps and auto-generated numbers etc. It might be worth having
pgpool in place anyway for your setup.
You could have a dual-attached disk system, and then when one machine
fails, the other could start up its postgresql server (but make sure
both never try to run at once).
I'd be tempted to look at pgpool sitting between your application and
the database, and then replication from the one machine to the other.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Guido Neitzer | 2005-12-14 16:19:17 | Re: Improving Availability |
Previous Message | Joshua D. Drake | 2005-12-14 15:41:40 | Re: ANN: PgBrowse 1.4 |