pgsql: Push enable/disable of notify and catchup interrupts all the way

Started by Tom Laneabout 21 years ago1 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Log Message:
-----------
Push enable/disable of notify and catchup interrupts all the way down
to just around the bare recv() call that gets a command from the client.
The former placement in PostgresMain was unsafe because the intermediate
processing layers (especially SSL) use facilities such as malloc that are
not necessarily re-entrant. Per report from counterstorm.com.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/backend/libpq:
be-secure.c (r1.56 -> r1.56.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c.diff?r1=1.56&r2=1.56.4.1)
pgsql/src/backend/tcop:
postgres.c (r1.440.4.1 -> r1.440.4.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.440.4.1&r2=1.440.4.2)
pgsql/src/include/tcop:
tcopprot.h (r1.73 -> r1.73.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/tcop/tcopprot.h.diff?r1=1.73&r2=1.73.4.1)