medium10 pts · first answer countsconnection-poolingpostgresql

Session state behind pgBouncer

After switching pgBouncer to transaction pooling, an app that runs SET search_path once at login starts hitting the wrong schema randomly. Why?

A.Transaction mode encrypts the SET commandB.pgBouncer rewrites schema names in queriesC.Each transaction may run on a different server connection, so session settings do not follow the clientD.search_path only works with MySQL

← Sizing shared_buffers Workers fighting over jobs →