[ python-Bugs-1003024 ] interrupting procedures

[noreply at pgfoundry.org]

Bugs item #1003024, was opened at 2007-04-12 14:24
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1003024&group_id=1000094

Category: BE/TEOP
Group: To do
Status: Open
Resolution: None
Priority: 4
Submitted By: James Pye (jwp)
Assigned to: James Pye (jwp)
Summary: interrupting procedures

Initial Comment:
Currently, there is no way to interrupt a pure-Python loop in a procedure.

The desire here is to allow SIGINTs to interrupt the Python interpreter. In many cases, the signal may get caught with Postgres' CHECK_INTERRUPTS(). However, if you're inside an interpreter loop that is not doing Postgres calls, it's simply not going to happen. Thus the need.

The only immediate solution is to extend teop to provide an interrupt handler that calls both the Python interrupt handler(rather, just set a Python exception) and the Postgres interrupt handler.

This also provides a way for slythe interrupts to be serviced.

The likely difficulty here is to do so portably. Also, there are likely to be numerous subtleties that need to be considered before implementing this.

----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1003024&group_id=1000094