Date: Sat, 24 Jan 2026 07:57:05 +0900 (JST)
Message-Id: <20260124.075705.464703586659216293.ishii@postgresql.org>
To: emond.papegaaij@gmail.com
Cc: pgpool-general@lists.postgresql.org
Subject: Re: Pgpool-II 4.7.0 released.
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: 
 <CAGXsc+YFWviCao8QF431ck3zeVmqXx_-riU-UeTxHVTOGA42qg@mail.gmail.com>
References: 
 <CAGXsc+a7d+EMDL0nqDVKch8OjCxQPK1o9Asu88M25bkS4VwXGA@mail.gmail.com>
	<20260123.190111.984289825765711614.ishii@postgresql.org>
	<CAGXsc+YFWviCao8QF431ck3zeVmqXx_-riU-UeTxHVTOGA42qg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20260124.075705.464703586659216293.ishii%40postgresql.org>
Precedence: bulk

>> wd_heartbeat_port was once in older versions of pgpool.conf,
>> e.g. v3.3.
> 
> Ah, that explains it. Perhaps we should review our configuration file
> against the manual to check if more options have changed over the
> years. We've been using pgpool for quite some time now. Thanks for the
> explanation.

The removal happend in 4.2.0 and it was explained in the release note.
https://www.pgpool.net/docs/42/en/html/release-4-2-0.html

See the section "A.25.2. Migration to Version 4.2":

>  Watchdog parameters below are deprecated.
> 
>     - wd_hostname
>     - wd_port
>     - wd_heartbeat_port <--- here
>     - heartbeat_device
>     - heartbeat_destination0
>     - heartbeat_destination_port0
>     - heartbeat_destination1
>     - heartbeat_destination_port1
>     - other_pgpool_hostname0
>     - other_pgpool_port0
>     - other_wd_port0
>     - other_pgpool_hostname1
>     - other_pgpool_port1
>     - other_wd_port1

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp