View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000553||Pgpool-II||[All Projects] General||public||2019-10-11 10:51||2019-10-29 13:24|
|Target Version||Fixed in Version|
|Summary||0000553: transaction mode in pgpool|
|Description||Hi Everyone, |
first of all, please forgive me if this bug tracker is not the proper place to ask questions.
In my current environment, I'm using both pgpool and pgbouncer. Basically our application connects on pgbouncer, which connects on pgpool and pgpool parses the queries and route them between our primary server and the database replicas.
I was wondering if can we use pgpool in the same "transaction mode" that pgbouncer does. is this possible?
btw, transaction mode means that the pool only holds the connection during a transaction and when it ends the connection is put back on the pool, making it available for other connections.
I saw that the connection_cache and max_pool parameters can enable a "connection cache" but its not clear if they work in the same way.
Thanks for your help!
|Steps To Reproduce||NA|
|Tags||No tags attached.|