| From: | Rafael Domiciano <rafael(dot)domiciano(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Downtime |
| Date: | 2009-02-16 19:52:37 |
| Message-ID: | 3a0028490902161152l13cc82eva6b26c013776cbcf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello for all,
Our bussiness do not tolerate anymore downtime (the downtime is estimate at
10 hour / year - that involves upgrade of hardware, crash of hardware), and
using Slony-I 1.2.15 I have waste time to put the slave node on production.
So I'm studying some replications softwares, like pgpool, pg_cluster,
pg_replicator.
Pgpool has a good idea, I can connect at 2 servers or more at the same time.
But I have some limitations, like Replication, Datas generated by the
servers (CURRENT_DATE, CURRENT_TIME, serial, oid); so I discarded it.
I tryed pg_cluster, but the documentation is very poor, and the installation
was unsuccesfull.
I would like to know from you what solution you uses for avoiding downtime,
so I could choose the solution that is best to my scenario and for others
that is begining in Postgres and is a little lost in replication.
Thnks for all,
Rafael Domiciano
DBA Postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-02-16 20:01:15 | Re: Downtime |
| Previous Message | Ray Stell | 2009-02-16 17:12:19 | standby role reversal |