Re: Connection.setReadOnly()
От | Greg Stark |
---|---|
Тема | Re: Connection.setReadOnly() |
Дата | |
Msg-id | 407d949e0912110409xc613b48p633d1bf36c1f650b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Connection.setReadOnly() (John R Pierce <pierce@hogranch.com>) |
Ответы |
Re: Connection.setReadOnly()
|
Список | pgsql-jdbc |
On Fri, Dec 11, 2009 at 12:57 AM, John R Pierce <pierce@hogranch.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
В списке pgsql-jdbc по дате отправления: