Re: timeout implementation issues - Mailing list pgsql-hackers

From Barry Lind
Subject Re: timeout implementation issues
Date
Msg-id 3CA9F9E0.9090302@xythos.com
Whole thread Raw
In response to Re: timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
Responses Re: timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
List pgsql-hackers
Since both the JDBC and ODBC specs have essentially the same symantics 
for this, I would hope this is done in the backend instead of both 
interfaces.

--Barry

Jessica Perry Hekman wrote:
> On Mon, 1 Apr 2002, Tom Lane wrote:
> 
> 
>>On the other hand, we do not have anything in the backend now that
>>applies to just one statement and then automatically resets afterwards;
>>and I'm not eager to add a parameter with that behavior just for JDBC's
>>convenience.  It seems like it'd be a big wart.
> 
> 
> Does that leave us with implementing query timeouts in JDBC (timer in the
> driver; then the driver sends a cancel request to the backend)?
> 
> j
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 




pgsql-hackers by date:

Previous
From: Bradley McLean
Date:
Subject: Re: Suggestions please: names for function cachability attributes
Next
From: Peter Eisentraut
Date:
Subject: Re: Suggestions please: names for function cachability