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

From Tatsuo Ishii
Subject Re: pg_ctl failover Re: Latches, signals, and waiting
Date
Msg-id 20110131.123547.671468322707979322.t-ishii@sraoss.co.jp
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
> 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. Because the trigger file is checked every for 5s,
> which would lengthen the failover time by an average 2.5s.

Ok, probably I could make the function smart enough to signal or not
by looking at the PostgreSQL version.

BTW is it possible to export following variable in xlog.c?

static char *TriggerFile = NULL;

That would make coding of the C function lot easier.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: SSI patch version 14
Next
From: Itagaki Takahiro
Date:
Subject: Re: pg_ctl failover Re: Latches, signals, and waiting