How pgbouncer care about session parameters in transaction pooling mode

Question

i connect to Postgresql via JDBC through pgbouncer with transaction pooling mode enabled. As far as I know in this mode pgbouncer can share same connection for several client without breaking session. So several clients may work within a single session sequentially, one by another. The question is does pgbouncer care about reseting session parameters when it detach one client from a connection and attach another client to this connection?

In particular, my app get connection and then issues something like this:

executeQuery(connection,"select set_config('myapp.user','fonar101',false)");
..../*other actions*/
commit(connection); 

After commit pgbouncer can detach my app from connection and get it back to its pool, right? So,

1. if I issue another statements after commit they will probably be executed within another session with incorrect values of session parameters
2. pgbouncer can attach another client to that connection and that client will proceed with again incorrect session settings

How does pgbouncer care about this things?

Answer 1

I'd say the opposite:

https://pgbouncer.github.io/config.html

transaction

Server is released back to pool after transaction finishes.

Which means that when you SET SESSION (default for SET), without specifying SET LOCAL, you change settings for all transactions that share the session in the pool...

Answer 2

According pgbouncer docs it doesnt support SET/RESET and ON COMMIT DROP for temp tables in transaction pooling mode.