From: | Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com> |
---|---|
To: | Mikko Partio <mpartio(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL clustering (shared disk) |
Date: | 2007-08-16 07:05:31 |
Message-ID: | 1187247931.2878.10.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On Thu, 2007-08-16 at 09:42 +0300, Mikko Partio wrote:
> The idea would be that the cluster programs with gfs (and HP ilo)
> would make sure that only one postmaster at a time would be able to
> access the shared disk, and in case the active node fails the cluster
> software would shift the services to the previously passive node.
AFAIK, it is the fence device that will prevent the postmaster access
from the failed node. RHCS will just switch the servers.
> What I'm pondering here is that is the cluster able to keep the
> postmasters synchronized at all times so that the database won't get
> corrupted.
Keep all the $PGDATA in the shared disk. That would minimize data loss
(Of course, there is still a risk of data loss -- the postmasters are
not aware of each other and they don't share each other's buffers, etc.)
Regards,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2007-08-16 07:58:30 | Re: PostgreSQL clustering (shared disk) |
Previous Message | Hannes Dorbath | 2007-08-16 07:01:23 | Re: PostgreSQL clustering (shared disk) |