| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG signal handler and non-reentrant malloc/free calls |
| Date: | 2011-03-01 23:42:34 |
| Message-ID: | AANLkTim8FVnrjSNqDCiXAvWGxmYnoVAzkvjrv48fL-8Z@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 1, 2011 at 3:11 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Heck, you can just put an Assert(!ImmediateInterruptOK) there, although it
> will fire in the authentication phase because of the issue with
> ClientAuthentication. You can set debug_assertions=off in postgresql.conf
> and enable it again with SET after logging in to get around that.
That doesn't sound like a bad idea. We could
Assert(!ImmediateInterruptOK || ImmediateInterruptEnabledInQuestionablePlace)
at the beginning of a bunch of basic low-level routines like AllocSetAlloc.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-03-02 00:05:12 | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |
| Previous Message | Nikhil Sontakke | 2011-03-01 23:30:07 | Re: PG signal handler and non-reentrant malloc/free calls |