Re: Fix WITHOUT OVERLAPS multirange with location replication

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: Zhijie Hou <houzhijie22(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, kedar anavardekar <kedar(dot)anavardekar(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Fix WITHOUT OVERLAPS multirange with location replication
Date: 2026-10-15 18:49:58
Message-ID: CA+renyWDQRyRbQwe-MZETBCmSB+Z4BfeNdpP7=uNcsUkUdMfUQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 13, 2026 at 5:16 AM Zhijie Hou <houzhijie22(at)gmail(dot)com> wrote:
>
> > Yeah, but keeping RI FULL also doesn't harm; rather it tests something
> > extra which is that it can extract required values from the full
> > tuple. So, I am okay either way. I have modified the comments at
> > multiple places in the patch as I find there is a lot of redundancy in
> > the comments. See attached top-up patch. BTW, we need a separate patch
> > for v18 as well.
>
> Thanks for the diff. I have merged and prepared the patches for
> back branches as well.

Thanks! These all apply and look good to me. I'll mark the CF entry as
Ready for Committer.

Yours,

--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-10-15 18:52:53 Reject COPY TO of unlogged relations during recovery
Previous Message Baji Shaik 2026-10-15 18:35:59 [PATCH] Doc fix for autovacuum_max_parallel_workers