RE: Fastpath error on solaris 2.8 pgsql 7.1.3

So I wanted to thank you. Indeed I did have a thread problem
in my application that caused the same connection to be used by
more than one thread at time. Thus the occassional problem
due to transactions being out of sync.

t.r. missner
level(3) communications

Chris -- you can explicity call myStatement.execute("BEGIN");
and myStatement.execute("COMMIT");
or you can simply use myConnection.setAutoCommit(true); or false when
finished.
This accomplishes the same thing as BEGIN/COMMIT.

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, August 27, 2001 2:43 PM
To: Missner, T. R.
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Fastpath error on solaris 2.8 pgsql 7.1.3

T(dot)R(dot)Missner(at)Level3(dot)com writes:
> FastPath call returned ERROR: lo_write: invalid large obj descriptor (0)

Usually this indicates that you didn't have the lo_open ... lo_write
... lo_close sequence wrapped in a transaction block (BEGIN/COMMIT
SQL commands). Since it's erratic for you, I'd bet that some of your
application control paths have the BEGIN and some don't.

regards, tom lane