Skip site navigation (1) Skip section navigation (2)

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

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, magnus(at)hagander(dot)net, heikki(dot)linnakangas(at)enterprisedb(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-31 03:31:12
Message-ID: AANLkTi=4+2O9GPCOnSa+8FMdrJY9cVkSa1OS2wPiRVa7@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Jan 31, 2011 at 11:52, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Sat, Jan 29, 2011 at 1:11 AM, Tatsuo Ishii <ishii(at)postgresql(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Jeff DavisDate: 2011-01-31 03:33:37
Subject: Re: SSI patch version 14
Previous:From: Shigeru HANADADate: 2011-01-31 03:27:55
Subject: Re: review: FDW API

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group