On Fri, Feb 27, 2009 at 9:52 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > > 2. Use a signal other than SIGQUIT for immediate shutdown of child > processes. We can't change the signal sent to postmaster for > backwards-compatibility reasons, but the signal sent by postmaster to child > processes we could change. We've already used all signals in normal > backends, but perhaps we could rearrange them.
This isn't the first time we've run into the problem that we've run out of signals. I think we need to multiplex all our event signals onto a single signal and use some other mechanism to indicate the type of message. Perhaps we do need two signals though, so subprocesses don't need to connect to shared memory to distinguish "exit now" from other events. SIGINT for "exit now" and USR1 for every postgres-internal signal using shared memory to determine the meaning sounds like the most logical arrangement to me. Do we really need a "promote to master" message at all? Is pg_standby responsible for this or could the master write out the configuration changes necessary itself? -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
