From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | aaliya zarrin <aaliya(dot)zarrin(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: To Signal The postmaster |
Date: | 2010-12-09 10:21:02 |
Message-ID: | AANLkTinvoXGjv=0hWPs-TEwg-VB=iyo+CUwzuG+EEULF@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 8, 2010 at 6:22 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Dec 8, 2010 at 4:59 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> For 9.1, we should think of a better way to do this, perhaps using SIGUSR1
>> to wake up. Maybe we won't even need the trigger file anymore.
>
> If we use SIGUSR1, the mechanism to allow the users to specify the event type
> seems to be required. For example, we should make the SIGUSR1 handler
> check not only the shmem (i.e., PMSignalStat) but also the file?
What I'm thinking is to make something like "pg_ctl promote" create the event
file specifying the standby promotion in $PGDATA/pg_event or elsewhere,
and send SIGUSR1 to postmaster. OTOH, when SIGUSR1 arrives, postmaster
checks whether that event file exists. If it does, postmaster removes it and
sends the signal to startup process for standby promotion.
Thought?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-12-09 11:12:15 | Re: Hot Standby tuning for btree_xlog_vacuum() |
Previous Message | Simon Riggs | 2010-12-09 09:48:25 | Re: On-the-fly index tuple deletion vs. hot_standby |