| From: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
|---|---|
| To: | Digimer <linux(at)alteeve(dot)com>, Andy <angelflow(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Tutorials on high availability Postgresql setup? |
| Date: | 2010-10-07 16:13:01 |
| Message-ID: | 979817.32324.qm@web29003.mail.ird.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> One option would be to create a simple 2-node cluster and run your PgSQL
> server in a migrateable VM backed by a SAN or, if your budget is more
> modest, a simple DRBD device.
>
> Personally, I like to use RHCS (Red Hat Cluster Services) with a DRBD
> array becking clustered LVM with Xen VMs (domU) on dedicated LVs. This
> doesn't dictate the OS version hosting postgres though, so if you've got
> a particular set of requirement, you can meet them.
>
> Then in the case of planned outage, you can hot-migrate your VM to the
> other node. In the case of catastrophic failure, the surviving node can
> boot the PgSQL server and it would come back as if it had simply lost
> power.
I'm interested in the subject... can you explain a little more the setup?
Thank you
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Zhao | 2010-10-07 16:35:03 | migration from PointBase to PostgreSQL |
| Previous Message | Tom Lane | 2010-10-07 15:40:33 | Re: pg_relation_size / could not open relation with OID # |