Received: from keyframe.cjas.org ([208.210.124.55]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA44554 for ; Thu, 29 Jul 1999 21:30:34 -0400 (EDT) (envelope-from garza@cjas.org) Received: from localhost (garza@localhost) by keyframe.cjas.org (8.9.3/8.9.2) with ESMTP id VAA00659 for ; Thu, 29 Jul 1999 21:30:34 -0400 (EDT) (envelope-from garza@cjas.org) Date: Thu, 29 Jul 1999 21:30:34 -0400 (EDT) From: John David Garza X-Sender: garza@localhost To: pgsql-interfaces@postgresql.org Subject: jdbc, pgsql6.5.1, large objects Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hey folks, Let's see, my admin just upgraded postgresql to 6.5.1 and now it looks like FastPath isn't working. More specifically, after creating and opening a large object using the LargeObjectManager class, any other access attempts throws the following: FastPath call returned ERROR: lo_write: invalid large obj descriptor (0) FastPath call returned ERROR: lo_write: invalid large obj descriptor (0) at postgresql.fastpath.Fastpath.fastpath(Fastpath.java:141) at postgresql.fastpath.Fastpath.fastpath(Fastpath.java:188) at postgresql.largeobject.LargeObject.write(LargeObject.java:173) at postgresql.largeobject.LargeObject.write(LargeObject.java:188) at uploadImage.main(uploadImage.java:87) In this case, line 87 in uploadImage is: ... 85 LargeObject pict = lobjm.open(num); 86 while ((s=fblob.read(buf, 0, 256)) > 0) { 87 pict.write(buf, 0, s);} ... Before upgrading to 6.5.1, this program worked fine. Calls to tell, size, read all cause the same type of exceptions. Any help would be appreciated. Other info: FreeBSD 3.2, jdk1.1.8 Thanks, John David Garza garza@keyframe.cjas.org