| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(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:44:30 |
| Message-ID: | AANLkTikdThxO=Q9zvut5TOMGAYAtGOr2ce-UwdnLFpc2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 31, 2011 at 12:31 PM, Itagaki Takahiro
<itagaki(dot)takahiro(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-01-31 03:49:45 | Re: pg_ctl failover Re: Latches, signals, and waiting |
| Previous Message | Itagaki Takahiro | 2011-01-31 03:42:47 | Re: Extensions support for pg_dump, patch v27 |