You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, looking for a general advice regarding postgres/pgbouncer/application pooling setup. Is it generally a good idea to have both application and pgbouncer level pooling enabled (transaction mode) ? Can the application pool for example save some resources/latency by avoiding opening a new connection (also maybe dns lookup, network, etc …) to pgbouncer for each transaction or is that a small enough penalty ? Can the application pooling when behind pgbouncer actually do some harm ? Thanks for any opinions/pointers 🙂
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, looking for a general advice regarding postgres/pgbouncer/application pooling setup. Is it generally a good idea to have both application and pgbouncer level pooling enabled (transaction mode) ? Can the application pool for example save some resources/latency by avoiding opening a new connection (also maybe dns lookup, network, etc …) to pgbouncer for each transaction or is that a small enough penalty ? Can the application pooling when behind pgbouncer actually do some harm ? Thanks for any opinions/pointers 🙂
Beta Was this translation helpful? Give feedback.
All reactions