Release 4.2.8

Release Date: 2022-02-17

A.3.1. Changes

  • Suppress message length log for in_hot_standby . (Tatsuo Ishii)

    PostgreSQL 14 introduced new config parameter in_hot_standby .

    The value is either "on" for standby servers or "off" for primary servers. As a result pgpool log is flooded by the messages:

         LOG:  reading message length
         DETAIL:  message length (22) in slot 1 does not match with slot 0(23)
        

    To avoid this, only complain if the parameter name is not in_hot_standby .

    Also the message is enhanced to show the parameter name. For example:

         LOG:  ParameterStatus "TimeZone": node 1 message length 30 is different from main node message length 24
        

    Discussion: [pgpool-hackers: 4076]

  • Add validations of wd_lifecheck_password and recovery_password format (Masaya Kawamoto)

    wd_lifecheck_password and recovery_password are not allowed to be md5 hashed password format but pgpool just reported authentication failure and did not check them.

  • Enhance parameter status handling. (Tatsuo Ishii)

    When a parameter status message arrives from backend Pgpool-II forwards it to frontend not just memorize.

A.3.2. Bug fixes

  • Fix long standing bug with pcp_node_info . (Tatsuo Ishii)

    Discussion: [pgpool-hackers: 4109]

  • Fix health check process issues pointed out by Coverity . (Tatsuo Ishii)

  • Fix memory leak pointed out by Coverity . (Tatsuo Ishii)

  • Fix failover() to deal with the case when no former primary node exists. (Tatsuo Ishii)

    In case Req_info->primary_node_id is -1 like no primary node exists when Pgpool-II starts up, failover() skipped to call find_primary_node_repeatedly() . Also follow_master_command was not executed.

    Discussion: [pgpool-hackers: 4113]

  • Fixed sample failover script. (Bo Peng)

    This script did not consider the case when the old primary node id is "-1".

  • Fixed the streaming replication check process not to retry if it cannot connect to the backend.( bug 742 ) (Bo Peng)

    This retry caused a long time failover.

A.3.3. Documents

  • Fix documentation typos. (pengbo)

    Patch is created by Umar Hayat.

  • Add "exclude" settings to /etc/yum.repos.d/pgdg-redhat-all.repo so that Pgpool-II is not installed from PostgreSQL YUM repository. (Bo Peng)

  • Add restriction regarding ParameterStatus and in_hot_standby parameter. (Tatsuo Ishii)

  • Add restriction about set_config . (Tatsuo Ishii)

A.3.4. Test tools

  • Fix pgpool_setup in failover script creation. (Tatsuo Ishii)

    When pgpool_setup creates failover.sh , it did not consider the case when no primary server existed.

A.3.5. Regression tests

  • Allow to run regression test against existing installation without recompiling. (Tatsuo Ishii)

    Discussion: [pgpool-hackers: 4077]

  • Fix regression test 075. (Tatsuo Ishii)

    The test reported success even if pgpool does not start up. Problem reported and patch provided by Qiang Lingjie. Discussion: [pgpool-hackers: 4085]

  • Fix pgpool_setup and watchdog_setup binary PATH in noinstall mode. (Bo Peng)