From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | masao(dot)fujii(at)gmail(dot)com, magnus(at)hagander(dot)net, heikki(dot)linnakangas(at)enterprisedb(dot)com, itagaki(dot)takahiro(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_ctl failover Re: Latches, signals, and waiting |
Date: | 2011-01-28 12:36:34 |
Message-ID: | AANLkTimO5AZetgAd2SejOFzj5F+N1Lu-Nphey0PDt+4=@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 28, 2011 at 3:40 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> On Fri, Jan 28, 2011 at 4:57 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> On Fri, Jan 28, 2011 at 08:44, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>>>>>> I did s/failover/promote. Here is the updated patch.
>>>>>
>>>>> I rebased the patch to current git master.
>>>>
>>>> I'm thinking about implementing a function which does a promotion for
>>>> the standby. It will make pgpool lot easier to control the promotion
>>>> since it allow to fire the promotion operation (either creating a
>>>> trigger file or sending a signal) via SQL, not ssh etc.
>>>
>>> I agree that having this available via SQL would be useful in a number
>>> of cases. pgpool or such being one, but also for example pgadmin.
>>
>> Agreed. I submitted the patch before, but I forgot to update it
>> and add it to CF.
>> http://archives.postgresql.org/message-id/AANLkTimuHbxbuM+zLkaEX3aDqSeiMUE3xb4ww1QtsLmf@mail.gmail.com
>
> Great!
I hate to be a wet blanket, but the number of patches in this CF is
going the wrong direction.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | JonY | 2011-01-28 13:09:40 | Re: mingw64 |
Previous Message | Andrew Dunstan | 2011-01-28 10:19:15 | Re: mingw64 |