[pgpool-general: 5876] Re: Pgpooladmin and pull request
pengbo at sraoss.co.jp
Fri Jan 19 14:24:00 JST 2018
We adopted your patch because we think we should use DB connection
timeout parameter to make pgpoolAdmin more useful.
We made the following changes based on your patch:
- Change the parameter name
_PGPOOL2_CONNECT_TIMEOUT -> _PGPOOL2_PG_CONNECT_TIMEOUT
- We set default value of _PGPOOL2_PG_CONNECT_TIMEOUT to 10s
because 5s is too short.
- Some translations are improved.
Thank you for your patch.
On Thu, 14 Dec 2017 10:45:26 +0400
Tuukka Kivilahti <Tuukka.Kivilahti at Kapsi.fi> wrote:
> I made some changes to pgpooladmin. In which format or how you want to have these changes?
> They are now in github, and can be seen from: https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout <https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout>
> On our clients enviroment, there is firewall between pgpool and postgresql -servers. If postgresql -server is down, this firewall will drop every packet which is going from pgpool to postgresql -server. When pgpooladmin tries to connect there, it will not get any answer from any network device -> it will wait really long time, and this makes pgpooladmin unusable in this situation. Added configurable timeout to pgppooladmins postgresql -connections, so it's still usable when one postgresql database is down.
> Tuukka Kivilahti
> Tuukka.Kivilahti at Kapsi.fi <mailto:Tuukka.Kivilahti at Kapsi.fi>
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
More information about the pgpool-general