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 AANLkTi=4+2O9GPCOnSa+8FMdrJY9cVkSa1OS2wPiRVa7@mail.gmail.com
Whole thread Raw
In response to Re: 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>)
List pgsql-hackers
On Mon, Jan 31, 2011 at 11:52, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Sat, Jan 29, 2011 at 1:11 AM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>> Ok. I will write a C user function and add to pgpool source tree. I
>> think it will be fairly easy to create a trigger file in the function.
>
> If the "pg_ctl promote" patch will have been committed, I recommend that
> the C function should send the signal to the startup process rather than
> creating the trigger file.

The C function needs to create a trigger file in $PGDATA/promote
before sending signals, no?    system("pg_ctl promote") seems
the easiest way if you use an external module.

-- 
Itagaki Takahiro


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: pg_ctl failover Re: Latches, signals, and waiting
Next
From: Itagaki Takahiro
Date:
Subject: Re: Extensions support for pg_dump, patch v27