Skip to Content
เมนู
คุณต้องลงทะเบียนเพื่อโต้ตอบกับคอมมูนิตี้
คำถามนี้ถูกตั้งค่าสถานะ
1 ตอบกลับ
5891 มุมมอง

Hi All,

I'm vexed by the issue of adding PGBouncer to existing 12.0 CE sites. The issue comes down to this:

  1. If I set pgbouncer.ini pool_mode = session, then everything works but there's no benefit from PGBouncer.

  2. If I set pgbouncer.ini pool_mode = transaction, then pooling is a benefit, but CRON and CHAT become inoperative.

To try and resolve Case 1, I've tried many pgbouncer.ini configurations.

To try and resolve Case 2, I've read Odoo and Openerp forums back to version 6, and tried many permutations of the suggestions using odoo-bin, odoo-gevent, 3rd party wsgi servers (gunicorn, cherrypy), CRON and CHAT listeners bypassing PGBouncer, etc.

Can anyone make some new qualified CONFIG or PROCESS or CODE suggestions for running 12.0 CE through PGBouncer and keeping CRON and CHAT features?

Many thanks!

George

อวตาร
ละทิ้ง
คำตอบที่ดีที่สุด

Hello. Yes. you are correct. Pg-bouncer or Pg-Pool-II does not work for Odoo. Odoo queries are in transactions. If you are looking for proxy for Odoo, check out the Heimdall Proxy: https://www.heimdalldata.com/odoo. It can support connection pooling, query caching, automated Postgres failover and Read/Write split with Strong Consistency.

อวตาร
ละทิ้ง
Related Posts ตอบกลับ มุมมอง กิจกรรม
1
ก.ค. 21
4345
0
ม.ค. 25
1053
2
ธ.ค. 24
8622
1
ก.ย. 24
41
1
ต.ค. 23
2214