| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Immediate shutdown and system(3) |
| Date: | 2009-03-18 20:16:51 |
| Message-ID: | 49C156B3.2000504@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Heikki Linnakangas wrote:
>> This should be mentioned in release notes, as any script that might be
>> using SIGQUIT at the moment needs to be changed to use SIGUSR1 or
>> SIGINT instead. Where should I make a note of that so that we don't
>> forget?
>
> Unless I'm missing it the use of signals to trigger failover is not
> documented AT ALL. So why anyone would expect such behaviour is
> something of a mystery.
Well, some people do read source code. If it was more widely known, I
would hesitate more to change it, though.
> Perhaps doing that would be even more important than release notes.
Agreed it should be documented.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-03-18 20:30:47 | Re: small but useful patches for text search |
| Previous Message | Andrew Dunstan | 2009-03-18 20:04:11 | Re: Immediate shutdown and system(3) |