Date: Fri, 22 Aug 2025 08:26:47 +0900 (JST)
Message-Id: <20250822.082647.288485281093236217.ishii@postgresql.org>
To: pgpool-hackers@lists.postgresql.org
Subject: Re: Enhance watchdog_setup
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: <20250820.151646.1640218512808280876.ishii@postgresql.org>
References: <20250820.151646.1640218512808280876.ishii@postgresql.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20250822.082647.288485281093236217.ishii%40postgresql.org>
Precedence: bulk

> A tool called "watchdog_setup" has been used to create a simple test
> cluster environment on localost for developing and testing
> Pgpool-II. It allows to create 3 watchdog node and 3 PostgreSQL server
> configuration by single command for example:
> 
> $ watchdog_set -wn 3 -n 3
> 
> The command is also used in our regression test.
> 
> One of the things that watchdog_setup does not support is, assigning
> VIP. This is a limitation by deign as it runs on a single
> host. However, I would like to test whether watchdog properly executes
> if_up_cmd or if_down_cmd, which could increase the test coverage.  In
> the attached patch, a new option "-vip [ip]" is added to
> watchdog_setup.  If ip is omitted, '127.0.0.1' is assumed.
> The parameters added by this option are followings:
> 
> delegate_ip = '127.0.0.1'
> if_up_cmd = '/usr/bin/echo "if_up_cmd executed"'
> if_down_cmd = 'usr/bin/echo "if_down_cmd executed"'
> arping_cmd = '/usr/bin/true'
> 
> Comments and suggestions are welcome.

Patch pushed to master branch.
Thanks.
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp