Re: Add a bound check to TidRangeEval - Mailing list pgsql-hackers

From David Rowley
Subject Re: Add a bound check to TidRangeEval
Date
Msg-id CAApHDvrFpttry31n1DZLPpmVJoeeUm8YJgSAFHcbrYwdRn=Zgg@mail.gmail.com
Whole thread Raw
In response to Re: Add a bound check to TidRangeEval  (Junwang Zhao <zhjwpku@gmail.com>)
List pgsql-hackers
On Sat, 14 Jun 2025 at 16:10, Junwang Zhao <zhjwpku@gmail.com> wrote:
>
> On Sat, Jun 14, 2025 at 11:27 AM David Rowley <dgrowleyml@gmail.com> wrote:
> > How about adding "We don't bother validating that trss_mintid is less
> > than or equal to trss_maxtid, as the scan_set_tidrange() table AM
> > function will detect that."
>
> Sounds good to me. This will naturally direct readers to the
> comments in scan_set_tidrange.

Thanks for looking. Pushed, after changing "detect" into "handle".

David



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Logical Replication slot disappeared after promote Standby
Next
From: Amit Kapila
Date:
Subject: Re: pg_recvlogical cannot create slots with failover=true