When I say that this problem is erratic, I mean that sometimes a given piece
of code works and sometimes it doesn't - not that some pieces work and some
don't (don't know if that helps).
How is a BEGIN indicated? I get a Connection, grab a Statement from it, and
run my query. Do I have to do anything special to tell Fastpath that I am
BEGINning a transaction?
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
Sent: Monday, August 27, 2001 4:43 PM
Subject: Re: [JDBC] Fastpath error on solaris 2.8 pgsql 7.1.3
> 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
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
In response to
pgsql-jdbc by date
|Next:||From: Mano lito||Date: 2001-08-28 11:13:34|
|Subject: next() and PreparedStatement|
|Previous:||From: Bhuvaneswari||Date: 2001-08-28 09:58:24|
|Subject: Regarding vacuumdb|