pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a
Дата
Msg-id 20060614012414.247D09FA38F@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Do a CHECK_FOR_INTERRUPTS immediately before terminating a fastpath
function call.  Previously, there may have been no CHECK_FOR_INTERRUPTS
at all in the fastpath code path, making it impossible to cancel an
operation such as \lo_import externally.  This addition doesn't ensure
you can cancel, since your SIGINT may arrive while the backend is idle
waiting for the client, but it gives the largest window we can easily
provide.  Noted while experimenting with new control-C code for psql.

Modified Files:
--------------
    pgsql/src/backend/tcop:
        fastpath.c (r1.87 -> r1.88)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/fastpath.c.diff?r1=1.87&r2=1.88)

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

Предыдущее
От: sdanforth@pgfoundry.org (User Sdanforth)
Дата:
Сообщение: bizgres - bizgres: Added inheritAll=false to the compileKETL target to
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Improve error detection and recovery in lo_import()/lo_export().