This may best be asked in the admin group – please don’t cross-post. Let’s keep all further discussion in the admin group.
A good starting place for you would be the PostgreSQL manual, specifically the chapter called “High Availability”:
http://www.postgresql.org/docs/current/interactive/high-availability.html
… also Pgpool:
http://pgfoundry.org/projects/pgpool/
… and Slony:
http://slony.info/
Cheers,
~p
-----Original Message-----
From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org] On Behalf Of Karthikeyan Sundaram
Sent: Friday, 13 April 2007 10:39
To: pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
Subject: [SQL] setting up a mirroring or replication database
Hi Team,
We are using Postgres 8.1.0 and in the plans to migrate to 8.2.3. Ours is a OLTP application. Publishers, advertisers and consumers use our system world wide. Right now it's not a very big database. But we are expanding our operations to Europe and US where we are expecting a moster growth.
I want to setup a mirroring database or replications database so that if one database crash, the load balancing database should take care or it. Not only that, if I am upgrading one database, the other should take the load.
I have never set this kind of replication or mirroring the database before. What are the steps and procedures to do this kind of setup.
Please advise.
Regards
skarthi
Live Search Maps – find all the local information you need, right when you need it. Find it!
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email.
Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments
