[pgpool-general: 6115] Re: Disadvantages of Explicit Connection Pooler !
Bo Peng
pengbo at sraoss.co.jp
Thu Jun 7 17:20:04 JST 2018
Hi,
> I have my project set up with Spring Boot’s HikariCP connection pooler which
> connects to my PgPool infrastructure running in Master -Slave & Load Balancing mode.
>
> Just wanted to know is there any disadvantage in above architecture? Is the pooling of database connections getting redundant?
Sorry, I am not familiar with HikariCP.
Pgpool-II may disconnect the connection (for example, due to failover or client_idle_limit).
When you combine Pgpool-II with other connection pooling software,
the connection pooling software will regard it as an error and disconnect.
If HikariCP will retry when disconnecting from Pgpool-II, I think
it should be ok.
On Wed, 06 Jun 2018 01:47:33 +0530
Nitish Kumar <itcell.mpwz at mp.gov.in> wrote:
> Hi Team,
>
> I have my project set up with Spring Boot’s HikariCP connection pooler which
> connects to my PgPool infrastructure running in Master -Slave & Load Balancing mode.
>
> Just wanted to know is there any disadvantage in above architecture? Is the pooling of database connections getting redundant?
>
> What should be the ideal approach ?
>
> Also it would be really helpful if you all could suggeste some ideal number for max_connections and like wise settings for both HikariCP & PgPool if We want to run our project in current setup.
>
> Hope to get a response!
>
> Regards,
> Nitish Kumar
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
More information about the pgpool-general
mailing list