Re: what to do when pg_cancel_backend() doesnt work? - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: what to do when pg_cancel_backend() doesnt work?
Date
Msg-id 20070605023628.GC24232@alvh.no-ip.org
Whole thread Raw
In response to Re: what to do when pg_cancel_backend() doesnt work?  (Michael Fuhr <mike@fuhr.org>)
List pgsql-general
Michael Fuhr escribió:
> On Mon, Jun 04, 2007 at 12:00:10PM -0400, Alvaro Herrera wrote:
> > Rhys Stewart escribió:
> > > a more readable version
> >
> > What is this buffer() function?
>
> Looks like the PostGIS buffer() function, which calls GEOSBuffer()
> in the GEOS library, which is where the code might be stuck.
>
> http://postgis.refractions.net/docs/ch06.html#id2527029
> http://geos.refractions.net/

Yeah, that's what Rhys told me by private email.  I suggested asking the
PostGIS guys, but if GEOS is intended to be a platform-neutral module, I
guess it's not very likely that they'll be adding a CHECK_FOR_INTERRUPTS
in the loops there.

(Peeking much further starts to get too time-consuming for me so I left
it at that.)

--
Alvaro Herrera                          Developer, http://www.PostgreSQL.org/
"El destino baraja y nosotros jugamos" (A. Schopenhauer)

pgsql-general by date:

Previous
From: Erwin Brandstetter
Date:
Subject: Re: There can be only one! How to avoid the "highlander-problem".
Next
From: "Ian Harding"
Date:
Subject: $libdir