| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timeout implementation issues |
| Date: | 2002-03-30 05:16:36 |
| Message-ID: | 200203300516.g2U5GaN02291@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2002-03-30 05:29:15 | Posix AIO in new Red Hat Linux |
| Previous Message | Tom Lane | 2002-03-30 04:36:39 | Re: timeout implementation issues |