[pgpool-general: 131] Healthcheck timeout not always respected

[Stevo Slavić]

Hello pgpool community,

When system is configured for security reasons not to return destination
host unreachable messages, even though health_check_timeout is configured,
socket call will block and alarm will not get raised until TCP timeout
occurs.

Not a C programmer, found some info that select call could be replace with
select/pselect calls. Maybe it would be best if PGCONNECT_TIMEOUT value
could be used here for connection timeout. pgpool has libpq as dependency,
why isn't it using libpq for the healthcheck db connect calls, then
PGCONNECT_TIMEOUT would be applied?

Regards,
Stevo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20120110/8969dbe4/attachment.htm>