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

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>

To: Itagaki Takahiro <itagaki.takahiro@gmail.com>

Cc: Tatsuo Ishii <ishii@postgresql.org>, magnus@hagander.net, heikki.linnakangas@enterprisedb.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org

Date: 2011-01-31T03:44:30Z

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 →

Remove rare corner case for data loss when triggering standby server.
- faa055057258 9.1.0 cited

On Mon, Jan 31, 2011 at 12:31 PM, Itagaki Takahiro
<itagaki.takahiro@gmail.com> wrote:
> The C function needs to create a trigger file in $PGDATA/promote
> before sending signals, no?

No. At least in the current patch, just receipt of SIGUSR2 causes the
startup process to end a recovery. The startup process doesn't check
the existence of $PGDATA/promote, though postmaster does.

>  system("pg_ctl promote") seems
> the easiest way if you use an external module.

Yeah, that's true.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center