| From: | Noel <noel(dot)faux(at)med(dot)monash(dot)edu(dot)au> |
|---|---|
| To: | Bryan Irvine <bryan(dot)irvine(at)kingcountyjournal(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Replication |
| Date: | 2003-09-23 00:55:47 |
| Message-ID: | 3F6F9A13.9070502@med.monash.edu.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Hi Bryan,
Bryan Irvine wrote:
>I'm creating a DB that is extremeley important to have running all the
>time. Not for the importance of the data, but rather to keep the
>maximum uptime for the users. The db actually gets dropped, and
>recreated and 1,000,000-ish records inserted every night. I would like
>to create an identical db on seperate hardware that, in the event of
>hardware failure, the users could use while the hardware is getting
>replaced. What is the best method (considering no money can be spent
>other than my time) to do this?
>
>
>
Have a look at pgrelicator http://pgreplicator.sourceforge.net/ or
postgreSQL-R
http://gborg.postgresql.org/project/pgreplication/projdisplay.php
Cheers
--
Noel Faux
Department of Biochemistry and Molecular Biology
Monash University
Clayton 3168
Victoria
Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno LEVEQUE | 2003-09-23 06:36:58 | Re: Referencing multiple primary keys from a single table. |
| Previous Message | Bruno Wolff III | 2003-09-22 22:33:54 | Re: Referencing multiple primary keys from a single table. |