| From: | petere(at)postgresql(dot)org (Peter Eisentraut) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Don't unblock SIGQUIT in the SIGQUIT handler This was possibly |
| Date: | 2009-12-16 23:05:00 |
| Message-ID: | 20091216230500.EA3A1753FB7@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Log Message:
-----------
Don't unblock SIGQUIT in the SIGQUIT handler
This was possibly linked to a deadlock-like situation in glibc syslog code
invoked by the ereport call in quickdie(). In any case, a signal handler
should not unblock its own signal unless there is a specific reason to.
Modified Files:
--------------
pgsql/src/backend/tcop:
postgres.c (r1.577 -> r1.578)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c?r1=1.577&r2=1.578)
pgsql/src/include/libpq:
pqsignal.h (r1.35 -> r1.36)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/pqsignal.h?r1=1.35&r2=1.36)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-12-17 03:17:29 | Re: pgsql: Fixed auto-prepare to not try preparing statements that are not |
| Previous Message | Peter Eisentraut | 2009-12-16 22:55:34 | pgsql: If there is no sigdelset(), define it as a macro. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-12-16 23:07:29 | Re: determine snapshot after obtaining locks for first statement |
| Previous Message | David E. Wheeler | 2009-12-16 22:58:52 | Re: PATCH: Add hstore_to_json() |