-----Original Message-----
From: Nicolas Huillard [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, March 14, 2000 9:33 AM
To: 'Bruce Momjian'; Ricardo Kleemann
Cc: [EMAIL PROTECTED]
Subject: RE: [ADMIN] pgsql and nfs
Here's my 2 pence worth.
If high availability is important, don't use commodity hardware - it will break.
Get a good quality box, put in a RAID system and then just use it to run Postgres.
Have the 'client' boxes access it over the network in the usual way.
TAKE REGULAR BACKUPS.
Although I have not done this myself, I seem to remember that within the Postgres
system (possibly in Postmaster) there is the ability to log all SQL statements etc.
You could then capture these statements, and repeat them on a second set-up. In this
way you have a hot-swap back for when something breaks.
The last thing to remember with high availability is this:
"Things WILL break"
>This question leads me to another one : can we do High Availability using Postgres.
>If one Postgres machine fails, is there a means to have another Postgres
>installation share the same databases, with the lastest data in them ?
>Is it a Postgres issue, or an hardware/system issue ?
>
>Nicolas Huillard
[snip]
-----------------------------------------
Gary Stainburn.
Work: http://www.ringways.co.uk mailto:[EMAIL PROTECTED]
REVCOM: http://www.revcom.org.uk mailto:[EMAIL PROTECTED]
-----------------------------------------
Murphy's Laws: (1) If anything can go wrong, it will.
-----------------------------------------
