Josh Berkus wrote:
> Oliver,
>
>> S_1 from client 1 might be a completely different query to S_1 from
>> client 2. The JDBC driver just numbers statements sequentially as they
>> are used.
>
> So, how does j2EE-side connection pooling handle this?
Err.. it is dealing with JDBC connections, not protocol level stuff, so
there's no issue with statement naming. The driver just does what it
normally does (maintains a mapping of query to statement name on each
connection). The usual J2EE connection pool model is different to what
pgbouncer apparently does as clients explicitly return connections to
the pool when no longer needed -- which effectively invalidates any
PreparedStatement objects they might still be holding -- and reobtain
them when later need.
-O
