Date: Fri, 05 Jun 2026 13:49:06 +0900 (JST)
Message-Id: <20260605.134906.38997665776014789.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 <ishii@postgresql.org>
In-Reply-To: <20260604.161440.589411300726741691.ishii@postgresql.org>
References: 
 <CACeKOO0-ctbkHnV978Hz6xF44R_9AGG6StjEH-V=M9k-VcyxQg@mail.gmail.com>
	<20260531.140928.1159580709730343176.ishii@postgresql.org>
	<20260604.161440.589411300726741691.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/20260605.134906.38997665776014789.ishii%40postgresql.org>
Precedence: bulk

Hi Nadav,

>>>   v5-0001-Fix-disable_load_balance_on_write-and-query-cache.patch
> 
> I updated the patch to:
> v2-0001-Fix-disable_load_balance_on_write-to-not-break-qu.patch
> 
> I slightly modifies the first line of the commit message, and the file
> name has been changed too. In v2 patch, I added test cases for
> disable_load_balance_on_write options. Currently it includes test
> cases for trans_transaction, dml_adaptive and always. Other than that,
> nothing has been changed since v1. I plan to push to all supported
> branches after the June minor releases.

pushed.

https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=1333d2ae88ac180db6ed423866086b31424a455e

Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp