Re: pg_ctl failover Re: Latches, signals, and waiting - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_ctl failover Re: Latches, signals, and waiting
Date
Msg-id AANLkTimXOAtZx6Cj+USbcsDbnaRvWA5T52tw_ykdF9PQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_ctl failover Re: Latches, signals, and waiting  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: pg_ctl failover Re: Latches, signals, and waiting  (Tatsuo Ishii <ishii@postgresql.org>)
Re: pg_ctl failover Re: Latches, signals, and waiting  (Fujii Masao <masao.fujii@gmail.com>)
Re: pg_ctl failover Re: Latches, signals, and waiting  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Fri, Jan 28, 2011 at 08:44, Tatsuo Ishii <ishii@postgresql.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.


> If there's enough interest, I will propose such a function for next CF.

Just as a reminder, remember that next CF means 9.2.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: WIP: RangeTypes
Next
From: Tatsuo Ishii
Date:
Subject: Re: pg_ctl failover Re: Latches, signals, and waiting