| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | aaliya zarrin <aaliya(dot)zarrin(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: To Signal The postmaster |
| Date: | 2010-12-08 07:59:27 |
| Message-ID: | 4CFF3ADF.9010307@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.12.2010 06:12, aaliya zarrin wrote:
> I can not used SIGHUP, as it is already in use.
> I want to wake up the postmaster once the trigger file is generated
> and tell it to switch over from standby mode.
> Is it possible?
SIGHUP works precisely because it is already in use. When you send
SIGHUP, the startup process will wake up immediately, and reload the
configuration file. Reloading the configuration file is unnecessary in
this case, but it will wake it up and it will notice the trigger file.
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.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-12-08 08:19:49 | Re: wCTE behaviour |
| Previous Message | Magnus Hagander | 2010-12-08 06:48:56 | Re: Final(?) proposal for wal_sync_method changes |