--On lördag, april 23, 2005 10.08.12 +1200 Oliver Jowett
<oliver@opencloud.com> wrote:
> Palle Girgensohn wrote:
>
>> First, we cannot see anything in our code that would offer the
>> possibility for two threads to get hold of the same postgresql
>> connection. There might be something we're missing, but the only changes
>> made from a working system is updates of postgresql and its JDBC driver,
>> so it's easy to suspect a bug in the jdbc driver...
>
> There's really no shared state between different connections -- they're
> each independent objects with their own protocol layer objects, TCP
> connection etc. So it's hard to see how there could be a bug where two
> different Connection objects end up using the same physical connection..
> I'd be more suspicious of your application or connection pool.
Honestly, so am I. Only some change in pg 8 or pg-jdbc-8.0 triggered the
problem. It has worked like a charm for ages before this upgrade. Still,
you're probably right, I'll have to find the problem in our own code.
/Palle
