Skip site navigation (1) Skip section navigation (2)

Re: Connection.setReadOnly()

From: Greg Stark <gsstark(at)mit(dot)edu>
To: 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 12:09:04
Message-ID: 407d949e0912110409xc613b48p633d1bf36c1f650b@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Fri, Dec 11, 2009 at 12:57 AM, John R Pierce <pierce(at)hogranch(dot)com> 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.
Postgres chooses not to have this unpredictable error and instead have
unpredictable space usage -- it's an inevitable engineering tradeoff.

However recent versions of Oracle have tried various strategies to
reduce the frequency of this error -- likewise recent versions of
Postgres have made efforts to reduce this issue as well. If you use
8.4 you should be much less likely to run into this problem.


-- 
greg

In response to

Responses

pgsql-jdbc by date

Next:From: Craig RingerDate: 2009-12-11 14:37:22
Subject: Re: Connection.setReadOnly()
Previous:From: John R PierceDate: 2009-12-11 01:54:09
Subject: Re: Connection.setReadOnly()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group