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 1um9O1-00Agyy-Cs for pgpool-hackers@arkaria.postgresql.org; Wed, 13 Aug 2025 11:11:17 +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 1um9Nz-00Edac-Te for pgpool-hackers@arkaria.postgresql.org; Wed, 13 Aug 2025 11:11:16 +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 1um9Nz-00EdaV-ON for pgpool-hackers@lists.postgresql.org; Wed, 13 Aug 2025 11:11:15 +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 1um9Nx-000Llf-15 for pgpool-hackers@lists.postgresql.org; Wed, 13 Aug 2025 11:11:15 +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=4OzYDY2n6/xfDuCtSpglXwIhpcf+SzgEtvOWsdExm/A=; b=VVG6Gq4hhpQabE+JGKzAcArWx8 977NXQ1g/m3yPlgBSpEPDlhtbVaxvd6IVg4xy0WX+pRmRODrJdSJL/uoCT2XKQ3om5jXU8KKYGPBu uYNSm8ZLavBbOsCY2QzLnXseX6rydALaof2Eazj+2CxKBeNtTrOkIYT0XQCVQL5YLatoWKgRc9WeE n3iCgXogkv+fs0hY++oo1o+JMTZsUsfgd3YdXayanrCgZR6gt47OmM7r6oqkr14in8WXtzlv1aORg eSAefI5vKz+QytqIBdEqErNyb5S+s9jHq3WBjuhEMMI3gSi9UalzcOfBV/MUAgfHCRomeMXOYI9M6 Cm4aUv1A==; Received: from [2409:11:4120:300:5181:20fa:ad39:90a5] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.96) (envelope-from ) id 1um9Nt-000ulq-1f for pgpool-hackers@lists.postgresql.org; Wed, 13 Aug 2025 11:11:12 +0000 Date: Wed, 13 Aug 2025 20:10:58 +0900 (JST) Message-Id: <20250813.201058.1085144912021648546.ishii@postgresql.org> To: pgpool-hackers@lists.postgresql.org Subject: Re: Proposal: emit warning if life check has not started yet From: Tatsuo Ishii In-Reply-To: <20250808.114734.428503094104035498.ishii@postgresql.org> References: <20250808.114734.428503094104035498.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:5181:20fa:ad39:90a5 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Currently lifecheck emits a log only when life check becomes > ready. This is inconvenient for admins since they need to watch log > file until life check is ready. This commit changes life check to emit > warnings periodically until life check has started. The interval of > the warnings is wd_interval * 10 seconds. However for the first time > at lifecheck starting, no warning is emitted since it is likely that > lifecheck is not ready at that point. > > Patch attached. Patch pushed with slight commit message changes. Thanks. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a85b848cc5e749051e3edfb892bdb366f7c23a31 -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp