No, it is still there with pgdev.307ay2.jdbc3.jar:
java.sql.SQLException: ERROR: large object 36405664 does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1240)
at org.postgresql.core.v3.QueryExecutorImpl.receiveFastpathResult(QueryExecutorImpl.java:462)
at org.postgresql.core.v3.QueryExecutorImpl.fastpathCall(QueryExecutorImpl.java:398)
at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:69)
at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:108)
at org.postgresql.fastpath.Fastpath.getInteger(Fastpath.java:120)
at org.postgresql.largeobject.LargeObject.<init>(LargeObject.java:89)
at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:167)
at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:152)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setBytes(AbstractJdbc2Statement.java:1017)
-----Original Message-----
From: Kris Jurka [mailto:books@ejurka.com]
Sent: Tuesday, October 26, 2004 12:01 AM
To: Alexey Yudichev
Cc: pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] Problems with protocol V3 after migration to latest driver
On Mon, 25 Oct 2004, Kris Jurka wrote:
> [ Fastpath code isn't aware of transaction state.]
I've fixed the problem I was seeing. Could you try the updated jar files
available from http://www.ejurka.com/pgsql/jars/alexey/ and see if the
slightly different problem you reported has gone away.
Kris Jurka