Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjBY8-009vt4-1w for pgpool-general@arkaria.postgresql.org; Fri, 23 Jan 2026 07:25:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vjBY6-00Gb7R-2L for pgpool-general@arkaria.postgresql.org; Fri, 23 Jan 2026 07:25:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjBY6-00Gb7I-1L for pgpool-general@lists.postgresql.org; Fri, 23 Jan 2026 07:25:42 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjBY3-001tQZ-0Q for pgpool-general@lists.postgresql.org; Fri, 23 Jan 2026 07:25:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=YZj8SAl1Q7VBnFROp57wy7cR5MBRSt4VB5718IWm6J4=; b=rMbl/u32SxlOk+GLkicKErfrgq zcpuOIk+tcPDE6Vep1srqSvRdYaPIE7STPMpsRnFvmr+iBN2Yo5TFLekfUwz3FAFwi59MnoH5rHY0 1TULbvY45St/ecLWzdloxAonLbiGWHQpRaHDK2WMN95ZSzHcGhqTAhCctixj9b0CDaZOK3gQ9b1xX 2qpc1/fOlz+ZvnEIQffNXBSHW4SCTr5QVmZ3Zk2E4tHcDs04h2xtEtKhJ8XWq6n8DzGF3lUXyalG9 e3LVYaVXaYtass9bEx07n61Atp+jnk9NiwuDyvcVtG4448Dw80gXfb/vnZw9UmkP66uBXTVcjZl/I hmck5u3Q==; Received: from 117.141.178.217.shared.user.transix.jp ([217.178.141.117] helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjBXy-004IRy-1G; Fri, 23 Jan 2026 07:25:37 +0000 Date: Fri, 23 Jan 2026 16:25:26 +0900 (JST) Message-Id: <20260123.162526.1291014725918553616.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 In-Reply-To: <20260123.133510.1195841695338539350.ishii@postgresql.org> References: <20260122.093003.1821723338788147775.ishii@postgresql.org> <20260123.133510.1195841695338539350.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Ok, so we will have following 4 new params? > > wd_listen_addresses > wd_listen_port > wd_heartbeat_listen_addresses > wd_heartbeat_listen_port After thinking more, I feel like it would be overkill to allow to specify multiple IPs for wd_listen_addresses and wd_heartbeat_listen_addresses. If so, we can decide to allow only 1 IP for each parameter and change the names to: wd_listen_address wd_heartbeat_listen_address What do you think? Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp