Re: [JDBC] Problems with Large Objects using Postgres 7.2.1

How do I do that?

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
Sent: Wednesday, April 09, 2003 2:31 PM
To: cjwhite(at)cisco(dot)com
Cc: pgsql-jdbc(at)postgresql(dot)org; pgsql-admin(at)postgresql(dot)org
Subject: Re: [JDBC] [ADMIN] Problems with Large Objects using Postgres
7.2.1

"Chris White" <cjwhite(at)cisco(dot)com> writes:
> The first and second are over the same connection. The third is over a
> different connection, but issued after the second transaction has
completed.

Oh? At this point I'm prepared to bet that the second transaction isn't
really committed when you think it is. Perhaps the "COMMIT" command
isn't getting flushed out to the backend on time. You might want to
turn on query logging and watch to see exactly what happens when.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly