Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a
Date
Msg-id 20060614012414.247D09FA38F@postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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 by date:

Previous
From: sdanforth@pgfoundry.org (User Sdanforth)
Date:
Subject: bizgres - bizgres: Added inheritAll=false to the compileKETL target to
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Improve error detection and recovery in lo_import()/lo_export().