From: | Joseph Hammerman <jhammerman(at)squarespace(dot)com> |
---|---|
To: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Recommendations for PGBouncer interacting with HikariCP |
Date: | 2019-08-22 01:03:37 |
Message-ID: | CAFZjsjBjD9FMRo36qJ9QK8Kzzkpv52q1XHvE2hqJoVmqnjG=eQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi pgsql-jdbc email distribution list,
We have recently added PGBouncer into our stack. We have done this in part,
to protect the database. Our Java userbase is accustomed to using HikariCP
/ Hibernate for connection pooling. They would prefer to continue to use
the connection pooler, in order to not have GC churn on connection spin up
and tear down (in addition to additional latency introduced by having to
perform the three-way handshake more often).
Is there any published material / does anyone have any knowledge of how
these tools should interact or not interact? HikariCP wants to keep many
long running idle_in_transaction connections open, which saturates the
backend connection pool.
Thanks in advance for any assistance anyone can provide,
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Nancarrow | 2019-08-22 05:39:11 | Re: Procedure support improvements |
Previous Message | David Wall | 2019-08-17 17:39:57 | Re: Transaction state on connection Idle/Open/Failed |