| pgpool-II 4.0.10 Documentation | |||
|---|---|---|---|
| Prev | Up | Appendix A. Release Notes | Next |
Release Date: 2016-12-26
Tightening up the watchdog security. (Muhammad Usama)
Now wd_authkey uses the HMAC SHA-256 hashing.
Add pgpool_adm extension in Pgpool-II RPM. (Bo Peng)
Fix occasional segfault when query cache is enabled. (bug 263) (Tatsuo Ishii)
Do not cancel a query when the query resulted in an error other than in native replication mode. (Tatsuo Ishii)
It was intended to keep the consistency, but there's no point in other than native replication mode.
Change the default value of search_primary_node_timeout from 10 to 300. (Tatsuo Ishii)
Prior default value 10 seconds is sometimes too short for a standby to be promoted.
Per [pgpool-general: 5026].
Fix the case when all backends are down then 1 node attached. (bug 248) (Tatsuo Ishii)
When all backends are down, no connection is accepted. Then 1 PostgreSQL becomes up, and attach the node using pcp_attach_node. It successfully finishes. However, when a new connection arrives, still the connection is refused because pgpool child process looks into the cached status, in which the recovered node is still in down status if mode is streaming replication mode (native replication and other modes are fine). Solution is, if all nodes are down, force to restart all pgpool child.
Do not use random() while generating MD5 salt. (Tatsuo Ishii)
random() should not be used in security related applications. To replace random(), import PostmasterRandom() from PostgreSQL. Also store current time at the start up of Pgpool-II main process for later use.
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)