| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Greg Stark *EXTERN*" <gsstark(at)mit(dot)edu>, "John R Pierce" <pierce(at)hogranch(dot)com> |
| Cc: | "Oliver Jowett" <oliver(at)opencloud(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Connection.setReadOnly() |
| Date: | 2009-12-11 15:20:36 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C2039380B6@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Greg Stark wrote:
>>> Does the Oracle driver not follow the JDBC spec here? Or is it just that
>>> long-term open transactions don't cause problems on Oracle?
>>
>> the latter
>
> Well eventually on Oracle you would get a "Snapshot too old" error.
Only if the long reading transaction has isolation level
SERIALIZABLE, because with READ COMMITTED it will not need very
old rows from the UNDO tablespace.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-11 15:26:26 | Re: Connection.setReadOnly() |
| Previous Message | Craig Ringer | 2009-12-11 14:37:22 | Re: Connection.setReadOnly() |