From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Julian Scarfe <julian(at)avbrief(dot)com> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgpool 2.5b2 released |
Date: | 2005-02-04 06:21:57 |
Message-ID: | 42031485.3070208@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>pgpool 2.5 has the capabilty to perform periodical health checking to
>>PostgreSQL.
>>
>>
>
>Since pgpool has this capability, how about including a hook that allows a
>script to be run when pgpool detects a problem with the master? That would
>allow action to be taken to investigate further and, if required, switchover
>or failover and promote the slave to master.
>
>
Because it is not the place of a connection management software
to failover. Failover should happen only if:
1. You have a specific set of criteria that is matched via a network/system
management software.
2. You do it yourself.
The last thing in the world you need is to fail over to a slave because
somebody accidently tripped over a network cord.
Sincerely,
Joshua D. Drake
>Julian Scarfe
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Attachment | Content-Type | Size |
---|---|---|
jd.vcf | text/x-vcard | 285 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-02-04 06:25:23 | Re: REPLICATION Solution for WINDOWS OS |
Previous Message | Tope Akinniyi | 2005-02-04 06:08:51 | REPLICATION Solution for WINDOWS OS |