| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Rafael Domiciano <rafael(dot)domiciano(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Downtime |
| Date: | 2009-02-16 20:01:15 |
| Message-ID: | dcc563d10902161201y79ea4at4f506a7bdf50c01c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Feb 16, 2009 at 12:52 PM, Rafael Domiciano
<rafael(dot)domiciano(at)gmail(dot)com> wrote:
> 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.
What exactly was not good enough about slony? We use it for automated
failover which is initiated by the application if it detects the
master go down. Works pretty well. Our downtime for unscheduled
maintenance is well under an hour a year with this setup.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2009-02-16 20:44:05 | tsearch2 migration 8.2 --> 8.3 |
| Previous Message | Rafael Domiciano | 2009-02-16 19:52:37 | Downtime |