From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: timeout implementation issues |
Date: | 2002-04-02 18:35:12 |
Message-ID: | 3CA9F9E0.9090302@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)postgresql(dot)org)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-02 18:39:30 | Re: timeout implementation issues |
Previous Message | Bruce Momjian | 2002-04-02 18:30:32 | Re: Contrib update |