Horton

Re: pg_ctl failover Re: Latches, signals, and waiting

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: masao.fujii@gmail.com, magnus@hagander.net, heikki.linnakangas@enterprisedb.com, itagaki.takahiro@gmail.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Date: 2011-01-28T12:36:34Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove rare corner case for data loss when triggering standby server.

On Fri, Jan 28, 2011 at 3:40 AM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>> On Fri, Jan 28, 2011 at 4:57 PM, Magnus Hagander <magnus@hagander.net> wrote:
>>> 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.
>>
>> 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