Re: "Hanging Connection" blocks access to table (JBossMQ)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Schaber <schabi(at)logix-tt(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: "Hanging Connection" blocks access to table (JBossMQ)
Date: 2006-10-13 14:35:14
Message-ID: 29655.1160750114@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Markus Schaber <schabi(at)logix-tt(dot)com> writes:
> Is there any possibility that we make a backend realize this SIGIO (or
> whatever it gets) when the connection is closed?

I don't think it'd be a net win to add cycles to every query to check
the connection every so often.

> The same is for very long running C-Code functions (like PostGIS
> geomUnion() on geometries with millions of vertices), those also tend to
> block the backend for long times, without any possibility to kill it
> except SIGKILL.

That's the fault of the C code ... it should be doing
CHECK_FOR_INTERRUPTS periodically in any long-running loops.

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Markus Schaber 2006-10-13 15:31:02 Re: "Hanging Connection" blocks access to table (JBossMQ)
Previous Message Guillaume Cottenceau 2006-10-13 14:27:22 Re: 'now' is sometimes not now - but current_timestamp is