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 1w4Xbc-002IM6-2B for pgpool-hackers@arkaria.postgresql.org; Mon, 23 Mar 2026 05:13:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w4Xba-00FSuk-1h for pgpool-hackers@arkaria.postgresql.org; Mon, 23 Mar 2026 05:13:34 +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 1w4Xba-00FSuc-1A for pgpool-hackers@lists.postgresql.org; Mon, 23 Mar 2026 05:13:34 +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.98.2) (envelope-from ) id 1w4XbW-00000000ZMC-3Qkt for pgpool-hackers@lists.postgresql.org; Mon, 23 Mar 2026 05:13:33 +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=JKRHXgXorYQDd4j9Y3ZLmg6CxCcVeOLIOZKl+UA3Kfo=; b=hnsfSgRUsoSlFVeroTM/3Pm5eS jmNDbLMFBOXpz51ZyaBMhu6fA+PGpO4q6tLvhNL5EhaJLUpegWyfNCjZSbDqAz4Uipu/gH4u3hfSv AA9dCqGRKeZCNW3tHvAH2gfAqktlcr3wBRDwGJI+LAQS4JdKrTU0RnCDUvuvaemjrLXdETtnBlKzj 5bNC77LYYu20tsVrOzLnFtuY9AX4rUDd8PssiLp9jcRU7UPYzEwr6RGxpsBP3H7vFlq9fr+PQfNR7 jFOAI61b0fX+clAl5DJlcVwHoRG5+J7TzVg61EIzaVFtgGIU7ZfWsaR1MYDLbkvyjcVd/b6qdjdAt Zs5lL1AQ==; Received: from [2409:11:4120:300:1205:1c20:ee5f:2118] (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 1w4XbS-0052Go-26; Mon, 23 Mar 2026 05:13:29 +0000 Date: Mon, 23 Mar 2026 14:13:15 +0900 (JST) Message-Id: <20260323.141315.1197840295971477812.ishii@postgresql.org> To: nadav@tailorbrands.com Cc: pgpool-hackers@lists.postgresql.org Subject: Re: Proposal: Recent mutated table tracking in memory From: Tatsuo Ishii In-Reply-To: References: <20260309.141839.397327759559519126.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 X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:1205:1c20:ee5f:2118 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Thank you for looking into this, fixing it and getting back to me. > > Looking forward to your update. It seems my commit fixed the issue. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=18f7f632de982d8fb5d0da2f2fdc48e26ac467e7 So, I continue the review. + + This feature requires to be configured + for monitoring replication delay from replicas. + Why this feature requires replication_delay_source_cmd to be set? Why can't we enable the feature as well when delay_threshold_by_time > 0? Both replication_delay_source_cmd and delay_threshold_by_time should provide standy delay in time, which provides enogh information to run the feature. 1. documentation - I get a compile error. openjade -wall -wno-unused-param -wno-empty -wfully-tagged -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t sgml -i output-html -V html-index pgpool.sgml openjade:loadbalance.sgml:1122:21:X: reference to non-existent ID "RUNTIME-CONFIG-TRACK-TABLE-MUTATION" Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp