Re: timeout implementation issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: timeout implementation issues
Date
Msg-id 200203300516.g2U5GaN02291@candle.pha.pa.us
Whole thread Raw
In response to Re: timeout implementation issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
List pgsql-hackers
Tom Lane wrote:
> Jessica Perry Hekman <jphekman@dynamicdiagrams.com> writes:
> > [snip]
> > My proposal, then, is that the Java driver should submit the
> > transaction request; wait for the timeout; if it goes off, submit a
> > cancel request; and then throw a SQLException. We would not handle
> > this in the backend at all.
> 
> > Bruce agreed that this was a good point to ask what the rest of the
> > hackers list thought. Any input?
> 
> I guess the $64 question is whether any frontends other than JDBC want
> this behavior.  If it's JDBC-only then I'd certainly vote for making
> JDBC handle it ... but as soon as we see several different frontends
> implementing similar behavior, I'd say it makes sense to implement it
> once in the backend.
> 
> So, what's the market?

There is clearly interest from all interfaces.  This item has been
requested quite often, usually related to client apps or web apps.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: timeout implementation issues
Next
From: Justin Clift
Date:
Subject: Posix AIO in new Red Hat Linux