From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | magnus(at)hagander(dot)net |
Cc: | masao(dot)fujii(at)gmail(dot)com, 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 08:09:50 |
Message-ID: | 20110128.170950.705053590885895719.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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.
>
>
>> 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.
Oh, I meant current CF (has started in January)
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2011-01-28 08:12:43 | Re: Transaction-scope advisory locks |
Previous Message | Magnus Hagander | 2011-01-28 07:57:59 | Re: pg_ctl failover Re: Latches, signals, and waiting |