Re: longjmp in psql considered harmful

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: longjmp in psql considered harmful
Дата
Msg-id 24166.1150052258@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: longjmp in psql considered harmful  (Martijn van Oosterhout <kleptog@svana.org>)
Ответы Re: longjmp in psql considered harmful  (Martijn van Oosterhout <kleptog@svana.org>)
Список pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> As it states in the comment, you can't remove the longjump because
> it's the only way to break out of the read() call when using BSD signal
> semantics (unless you're proposing non-blocking read+select()). So the
> patch sets up the sigjump just before the read() and allows the routine
> to return. If you're not waiting for read(), no sigjump is done.

I think you're missing my point, which is: do we need control-C to
force a break out of that fgets at all?
        regards, tom lane


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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pl/tcl regression failed