Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA72452
	for <pgsql-interfaces@postgreSQL.org>;
	Fri, 30 Jul 1999 09:58:49 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA11034;
	Fri, 30 Jul 1999 09:57:43 -0400 (EDT)
To: John David Garza <garza@cjas.org>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects 
In-reply-to: Your message of Thu, 29 Jul 1999 21:30:34 -0400 (EDT)
	<Pine.BSF.4.10.9907292129190.46423-100000@localhost>
Date: Fri, 30 Jul 1999 09:57:43 -0400
Message-ID: <11032.933343063@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

John David Garza <garza@cjas.org> writes:
> FastPath call returned ERROR:  lo_write: invalid large obj descriptor (0)

This is achieving FAQ status very rapidly.  6.5 enforces the rule that
large object descriptors can only be used within a single transaction.
(This rule has always been in the documentation, but prior releases
didn't check, and most of the time referring to an LO opened in an
old transaction would still work...)

So you need an explicit begin/end transaction around your lo_open ...
lo_close sequence.  In JDBC I think you gotta turn off autocommit,
but I'm not familiar enough with JDBC to quote exact commands for you.

			regards, tom lane