| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Lazaro Ruben Garcia Martinez <lgarciam(at)estudiantes(dot)uci(dot)cu> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgresql cluster on SAN |
| Date: | 2010-09-09 03:32:37 |
| Message-ID: | 4C885555.9060108@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/09/2010 11:02 AM, Lazaro Ruben Garcia Martinez wrote:
> Thank you very much for your answer, In the cluster that i said before I need only failover.
> In the documentation of postgresql I read about the Shared Disk Failover, this tecnique avoids synchronization overhead by having only one copy of the database. It uses a single disk array that is shared by multiple servers. If the main database server fails, the standby server is able to mount and start the database as though it was recovering from a database crash. This allows rapid failover with no data loss. One disadvantage is that the standby server should never access the shared storage while the primary server is running.
> For these resons is posible to use a SAN?
Yes. See:
http://wiki.postgresql.org/wiki/Shared_Storage
Setting it up isn't trivial and if you mess it up, you *WILL* get
massive data corruption. If your shared storage dies, you still lose all
your data.
Personally, I favour replication.
Anyway, added a reference to [[Shared_Storage]] for failover-only
clustering to the faq entry posted earlier.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick | 2010-09-09 04:12:11 | Dynamically update NEW columns in plpgsql trigger |
| Previous Message | Scott Marlowe | 2010-09-09 03:10:58 | Re: postgresql cluster on SAN |