Re: [HACKERS] statement level trigger causes pltcl, plpython

Поиск
Список
Период
Сортировка
От Joe Conway
Тема Re: [HACKERS] statement level trigger causes pltcl, plpython
Дата
Msg-id 3F2EB823.50509@joeconway.com
обсуждение исходный текст
Ответ на Re: [HACKERS] statement level trigger causes pltcl, plpython SIGSEGV  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-patches
Tom Lane wrote:
> BTW, one other stylistic nit: I don't think comments like
>
>         /* internal error */
>         elog(ERROR, "unrecognized OP tg_event: %u", tdata->tg_event);
>
> are really necessary.  In the brave new ereport world, any elog(ERROR)
> call is an internal error by definition --- if it isn't, you should be
> using ereport.  So the use of elog is sufficient documentation.  IMHO
> anyway.

Yeah, I agree. During the conversion, I did that mostly to show that it
was a conscious decision. Going forward, every new elog (versus ereport)
*is* a conscious decision, or at least should be.

Joe



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] statement level trigger causes pltcl, plpython SIGSEGV
Следующее
От: Anne Dudfield
Дата:
Сообщение: Patch for select() -> poll() in libpq