Unix Technical Forum

pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a

This is a discussion on pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Do a CHECK_FOR_INTERRUPTS immediately before terminating a fastpath function call. Previously, there may have been no ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Committers

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-10-2008, 07:30 PM
Tom Lane
 
Posts: n/a
Default pgsql: Do a CHECK_FOR_INTERRUPTS immediately before terminating a

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/cvsw...1=1.87&r2=1.88)

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 07:21 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com