Re: PG signal handler and non-reentrant malloc/free calls

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: PG signal handler and non-reentrant malloc/free calls
Дата
Msg-id AANLkTim8FVnrjSNqDCiXAvWGxmYnoVAzkvjrv48fL-8Z@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PG signal handler and non-reentrant malloc/free calls  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
On Tue, Mar 1, 2011 at 3:11 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Nikhil Sontakke
Дата:
Сообщение: Re: PG signal handler and non-reentrant malloc/free calls
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)