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

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Push enable/disable of notify and catchup interrupts all the way
Date: 2005-06-02 21:04:30
Message-ID: 20050602210430.CA3D152894@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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:
----
REL7_3_STABLE

Modified Files:
--------------
pgsql/src/backend/libpq:
be-secure.c (r1.15.2.12 -> r1.15.2.13)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c.diff?r1=1.15.2.12&r2=1.15.2.13)
pgsql/src/backend/tcop:
postgres.c (r1.307.2.1 -> r1.307.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.307.2.1&r2=1.307.2.2)
pgsql/src/include/tcop:
tcopprot.h (r1.51 -> r1.51.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/tcop/tcopprot.h.diff?r1=1.51&r2=1.51.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-06-03 16:36:51 pgsql: Done: > * -Change WAL to use 32-bit CRC, for performance reasons
Previous Message Tom Lane 2005-06-02 21:04:08 pgsql: Push enable/disable of notify and catchup interrupts all the way