| 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:33:11 |
| Message-ID: | 20260604.163311.1423441645824043920.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-hackers |
> Amazing news! Thank you so much!
You are welcome!
> When can I expect it to be live in a version then ?
It will get into v4.8, which is supposed to be released in this
December.
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
> Nadav Shatz
> Tailor Brands | CTO
>
> On Thu, Jun 4, 2026 at 10:14 AM Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>
>> 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
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nadav Shatz | 2026-06-04 08:55:12 | Re: Proposal: Recent mutated table tracking in memory |
| Previous Message | Nadav Shatz | 2026-06-04 07:16:02 | Re: Proposal: Recent mutated table tracking in memory |