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.94.2) (envelope-from ) id 1ue6XO-00554u-7Q for pgpool-general@arkaria.postgresql.org; Tue, 22 Jul 2025 06:31:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ue6XL-005QLk-PP for pgpool-general@arkaria.postgresql.org; Tue, 22 Jul 2025 06:31:40 +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.94.2) (envelope-from ) id 1ue6XL-005QLc-Jp for pgpool-general@lists.postgresql.org; Tue, 22 Jul 2025 06:31:39 +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 1ue6XJ-0009gZ-32 for pgpool-general@lists.postgresql.org; Tue, 22 Jul 2025 06:31:38 +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:To:Message-Id:Date:Sender: Reply-To:Cc:Content-ID:Content-Description; bh=WpApYsdcf8r0VDBxIauFcs+A5joyqML/h85nM9Oo+g8=; b=DXonVmQNw/bXqFzo2uNrzjesUq swuTJC487NwlSIKktaLdRbXGd0pFnJJzsJ8iUNWyknP2XqpJSM1xXkRnDNjmL9KYBJGjPoVLDPIkS fOn6ePwvD0zi1a8fjryKcPyAo7FRpJ2MFqmP2egfeozPfyPuUkg4iWI4XTM/Zn228O1v4WB60AxUt e5vPJO6gXWv4rlE8RqU+aTuRF/U9fRryNNHrscdDRVKrrPXFT5mnCNtFDBv5H4XS6cYFGGk6+5bcN dgGZbtgE9NWvQPncKXcdwgQBFjeCXoG5P0t3McjzIP1IfSqei6TPijAByGaaSyVDARKWaYMKOfJfE 2BHRBP0w==; Received: from [2409:11:4120:300:725c:7a5a:3fd8:451e] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.96) (envelope-from ) id 1ue6XE-000QZb-1p for pgpool-general@lists.postgresql.org; Tue, 22 Jul 2025 06:31:35 +0000 Date: Tue, 22 Jul 2025 15:31:30 +0900 (JST) Message-Id: <20250722.153130.1007226654125839063.ishii@postgresql.org> To: pgpool-general@lists.postgresql.org Subject: Re: [pgpool-general: 9486] Retiring slony mode From: Tatsuo Ishii In-Reply-To: <20250529.180921.956428215680913984.ishii@postgresql.org> References: <20250529.180921.956428215680913984.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:725c:7a5a:3fd8:451e (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk From: Tatsuo Ishii Subject: [pgpool-general: 9486] Retiring slony mode Date: Thu, 29 May 2025 18:09:21 +0900 (JST) Message-ID: <20250529.180921.956428215680913984.ishii@postgresql.org> > Currently Pgpool-II accepts "slony mode" for backend_clustering_mode, > to support Slony-I (https://www.slony.info/). The latest Slony-I was > released in 2022, nearly 3 years ago. I, as a developer of Pgpool-II, > would like to retire Slony-I support, possibly in 4.7. If you are a > slony mode user, please speak up now. I have heard nothing since May 29. So I will start to work on retiring slony mode soon. Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp