| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net>, postgres jdbc <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: "Idle in Transaction" revisited. |
| Date: | 2004-09-18 22:16:48 |
| Message-ID: | 414CB3D0.8020800@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Tom Lane wrote:
> Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net> writes:
>
>>Are you saying that I will see stale database state at the logical
>>"start" of my transaction from a pooled connection?
>
>
>>That's a showstopper for sure. If I'm confused please enlighten me.
>
>
> Apparently you are confused, because the JDBC behavior has always
> been like that; it's only the current devel driver that fixes it.
That's not entirely true; 7.3-era drivers (which I think is what is
being used here) used "set autocommit" rather than explicit BEGIN. It
went back to using BEGIN again when 7.4 removed that option.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-09-18 22:21:16 | Re: "Idle in Transaction" revisited. |
| Previous Message | John R Pierce | 2004-09-18 22:08:53 | Re: Issues regarding code license of ported code. |