안녕하세요,
pgbouncer 대신 pgpool II를 Discourse와 함께 사용해 본 경험이 있는 분이 계신지 궁금합니다. 있다면, 지금까지 사용感は 어떠셨나요?
팀 입장에서는 어떤 시점에 pgpool II를 고려할 생각이 있으신가요? 있다면 그 이유는 무엇인가요?
감사합니다.
Ismael
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.
Many thanks Sam. Indeed, as you said for not many connections it might not make sense. Also, having transaction pooling into consideration there is only one winner in this case.
However, as far as I know, I saw pgbouncer does not offer HA, while pgpool II does. What about having a pgbouncer “in-front” of a pgpool to allow such feature? What’s the recommendation for a HA approach that fits well for Discourse?
Discourse offers HA out of the box using global configuration.
See: GitHub - discourse/rails_failover · GitHub
And dig through global settings here: discourse/config/discourse_defaults.conf at main · discourse/discourse · GitHub
You would configure 2 pgbouncers in a high availability / enormous amount of connections required mode.