This looks like you have either not got AutoCommit set to false, or are
calling commit() between calls. As of 6.5.x LargeObjects need to be
wrapped within a transaction, but if I'm right, all open LO's are closed
on commit().
Peter
--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
-----Original Message-----
From: Jason Venner [mailto:jason@idiom.com]
Sent: 13 September 1999 05:31
To: pgsql-hackers@hub.org
Subject: [HACKERS] jdbc1 large objects and 651 -- does it work for
anyone
Calling setBytes or any attempt to do LargeObject.write(byte[])
returns
[on the java side]
Oid gotten from lom.create() is 641377
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 RestoreBlobs.main(RestoreBlobs.java:298)
The -d3 log of the postmaster has
nitPostgres
StartTransactionCommand
query: set datestyle to 'ISO'
ProcessUtility: set datestyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: select proname, oid from pg_proc where proname = 'lo_open' or
proname = 'lo_close' or proname = 'lo_creat' or proname = 'lo_unl\
ink' or proname = 'lo_lseek' or proname = 'lo_tell' or proname =
'loread' or proname = 'lowrite'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
CommitTransactionCommand
StartTransactionCommand
CommitTransactionCommand
StartTransactionCommand
ERROR: lo_write: invalid large obj descriptor (0)
AbortCurrentTransaction
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
************
