From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Barry Lind" <blind(at)xythos(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [JDBC] Strange server error with current 8.0beta driver |
Date: | 2004-11-23 15:09:51 |
Message-ID: | 26577.1101222591@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
"Barry Lind" <blind(at)xythos(dot)com> writes:
> OK, getting closer. The error happens if in jdbc I reuse
> PreparedStatement objects to reexecute the same set of queries multiple
> times.
The TRAP you showed looked like it might have something to do with
trying to execute code outside any transaction. But I dunno how it got
there.
> If you still need a test case, let me know, and I will continue to
> package up what I have been working on.
What I'd actually rather have is a list of the exact sequence of
messages sent to the server.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bort, Paul | 2004-11-23 15:31:04 | Re: [Testperf-general] Re: ExclusiveLock |
Previous Message | Doug McNaught | 2004-11-23 15:08:25 | Re: [Testperf-general] Re: ExclusiveLock |
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Nasardinov | 2004-11-23 15:15:29 | Re: Can't throw the dreaded 'idle in transaction' - need help! |
Previous Message | Vadim Nasardinov | 2004-11-23 14:25:30 | better logging on the backend (was: Re: When running with autocommit false only the first BEGIN) |