RE: RE: fastpath error?

Hello.

I'm still having problems with this FastPath error.  As I mentioned,
autoCommit is always set to 'false' in our system, so could there be another
source of this?

Another angle - Can it be ignored?  For example, if I get the error during
lo_close and ignore it, am I okay?  If so, what exception am I looking for?
From the stack trace, it seems that it's just a java.lang.Exception - not a
SQLException....Do I just grab the text of the exception and look for
"FastPath" or is there a better way?

I really appreciate your help.
chris


-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of chris markiewicz
Sent: Thursday, April 12, 2001 9:36 AM
To: 'Peter Mount'; pgsql-general@postgresql.org;
pgsql-jdbc@postgresql.org
Cc: chris.markiewicz@commnav.com
Subject: [JDBC] RE: fastpath error?


Regarding the fastpath error (ERROR:  lo_close: invalid large obj descriptor
(0)...i also get this with lo_tell, etc)...

is there any possible cause that is not related to autoCommit?  our app does
a lot of transactional stuff so autocommit is set to false for all
connections (i added some logging that shows me the autocommit attribute and
it's false even when this error occurs)...i still see this problem
occasionally/randomly.

i appreciate your help.
chris

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of Peter Mount
Sent: Thursday, March 29, 2001 4:13 AM
To: cmarkiew@commnav.com; pgsql-general@postgresql.org
Subject: Re: fastpath error?


At 07:56 28/03/01 -0500, chris markiewicz wrote:
>Hello.
>
>I am occasionally (seemingly randomly) seeing the following error when I
try
>to load a large object.
>
>FastPath call returned ERROR:  lo_close: invalid large obj descriptor (0)

You must setAutoCommit(false) before using any large object.

Can someone give me some insight on this?  Can I call lo_close explicitly if
>i get this error?  Can I ignore it or will that leave me with open
>resources?

There are no open resources at the time of the error. Because lo's need to
be within a transaction when the transaction closes, so do the lo's.

Peter


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster