Timeline for Is it good practice to use both PGBouncer and PGPool together?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30 at 9:15 | answer | added | MOHAMED AMMAHA | timeline score: -1 | |
| Mar 14 at 7:32 | comment | added | goodfella |
Hi @LaurenzAlbe, we have a similar situation as we having application layer connection pooling using pg.pool client lib in node.js forwarding to an LB then routing to two pgbouncer. Later we planning to change pooling method to transaction in pgbouncer. Can you advise is it good or bad to have two layer of pooling?
|
|
| Oct 29, 2021 at 6:53 | comment | added | Laurenz Albe | I understand your reluctance to use pgPool, but if you want to use it for separating reads and writes, you might as well use it for pooling too. Or does that really cause additional pain? No tool can reliably tell if a statement will only read. I personally would opt for changing the application. Are you aware that you might not see a change performed on the primary on the standby immediately? | |
| Oct 29, 2021 at 5:30 | comment | added | Pramod | @LaurenzAlbe true but pgpool connection pooling is not that performant and takes more memory as well while pgbouncer is light weight and performs much better. If not pgpool are there any tools which allow us to do read and write splits without changing application code ? | |
| Oct 27, 2021 at 14:35 | comment | added | Laurenz Albe | Since pgPool is also a connection pooler, it doesn't make sense to me to use both pgBouncer and pgPool. | |
| S Oct 26, 2021 at 10:19 | review | First questions | |||
| Oct 26, 2021 at 15:15 | |||||
| S Oct 26, 2021 at 10:19 | history | asked | Pramod | CC BY-SA 4.0 |