# Pgbouncer מול pgpool II

**URL:** <https://meta.discourse.org/t/pgbouncer-vs-pgpool-ii/188981>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [3 במאי,‏ 2021,‏ 12:24pm UTC](https://meta.discourse.org/t/pgbouncer-vs-pgpool-ii/188981 "2021-05-03T12:24:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [4 במאי,‏ 2021,‏ 12:29am UTC](https://meta.discourse.org/t/pgbouncer-vs-pgpool-ii/188981/2 "2021-05-04T00:29:19Z")

</div>

pgpool II has no transaction pooling. Without transaction pooling it has extreme limited value in high scale hosting and would only add complexity.

On a standard “self hosted” Discourse you would be struggling to push 30-60 active connections and PG is not going to struggle with that. No need for a connection pooler to add complexity to your setup.

---

_[View the full topic](https://meta.discourse.org/t/pgbouncer-vs-pgpool-ii/188981)._
