pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a
Date: 2006-06-14 01:24:14
Message-ID: 20060614012414.247D09FA38F@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-06-14 01:28:55 pgsql: Improve error detection and recovery in lo_import()/lo_export().
Previous Message User Sdanforth 2006-06-14 00:23:24 bizgres - bizgres: Added inheritAll=false to the compileKETL target to