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

From Itagaki Takahiro
Subject Re: pg_ctl failover Re: Latches, signals, and waiting
Date
Msg-id AANLkTik2XxiuzgV=Ft5yWUcukWN3c4AViMhSm2aP9TTx@mail.gmail.com
Whole thread Raw
In response to pg_ctl failover Re: Latches, signals, and waiting  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: pg_ctl failover Re: Latches, signals, and waiting  (Fujii Masao <masao.fujii@gmail.com>)
Re: pg_ctl failover Re: Latches, signals, and waiting  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Jan 13, 2011 at 00:14, Fujii Masao <masao.fujii@gmail.com> wrote:
>> pg_ctl failover ? At the moment, the location of the trigger file is
>> configurable, but if we accept a constant location like "$PGDATA/failover"
>> pg_ctl could do the whole thing, create the file and send signal. pg_ctl on
>> Window already knows how to send the "signal" via the named pipe signal
>> emulation.
>
> The attached patch implements the above-mentioned pg_ctl failover.

I have three comments:
- Will we call it "failover"? We will use the command also in "switchover" operations. "pg_ctl promote" might be more
neutral,but users might be hard to imagine replication feature from "promote".
 

- pg_ctl should unlink failover_files when it failed to send failover signals.

- "standby_triggered" variable might be renamed to "failover_triggered" or so.

-- 
Itagaki Takahiro


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add support for logging the current role
Next
From: Itagaki Takahiro
Date:
Subject: Re: pg_regress multibyte setting