Re: Add a bound check to TidRangeEval

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Junwang Zhao <zhjwpku@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-06-14T05:20:42Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve comments for TidRangeEval
- 2f98f967fa78 18.0 landed

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