From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Elior Soliman <elior(dot)soliman(at)correlix(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: High Availability with Postgres |
Date: | 2010-06-20 17:36:35 |
Message-ID: | 20100620173635.GA24134@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jun 20, 2010 at 07:34:10PM +0300, Elior Soliman wrote:
> Hello,
>
> My company looking for some solution for High availability with Postgres.
>
> Our optional solution is as follows :
> Two DB servers will be using a common external storage (with raid).
Stop right there. This is the Oracle way of doing things, and it
doesn't work for PostgreSQL.
> Both servers are going to use the same DB files on the storage (as
> active/passive)
>
> Now I'm trying to understand how Postgres can work with this
> configuration. I.e :
It does not.
There are plenty of ways to get that broad spectrum of sometimes
contradictory things people mean when they use the phrase "HA" with
PostgreSQL, but you must first define your requirements. Once you
have done so, it will be possible to create strategies for achieving
same.
What are the actual requirements? Things that would be nice to have?
What are your priorities for both?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2010-06-20 17:37:42 | Re: High Availability with Postgres |
Previous Message | Elior Soliman | 2010-06-20 16:34:10 | High Availability with Postgres |