Re: Proposal: Recent mutated table tracking in memory

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: nadav(at)tailorbrands(dot)com
Cc: pgpool-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal: Recent mutated table tracking in memory
Date: 2026-06-04 07:14:40
Message-ID: 20260604.161440.589411300726741691.ishii@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-hackers

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.

After finishing review for your patch, I will push your patch along
with addition to 006.memqcache so that it tests the new option.

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

Attachment Content-Type Size
v2-0001-Fix-disable_load_balance_on_write-to-not-break-qu.patch text/x-patch 9.9 KB

In response to

Responses

Browse pgpool-hackers by date

  From Date Subject
Next Message Nadav Shatz 2026-06-04 07:16:02 Re: Proposal: Recent mutated table tracking in memory
Previous Message Tatsuo Ishii 2026-05-31 05:09:28 Re: Proposal: Recent mutated table tracking in memory