| From: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add a bound check to TidRangeEval |
| Date: | 2025-06-08 09:41:17 |
| Message-ID: | CAEG8a3KUbUUqQgfK5X8Sj-+ppPtGNTU+Ziep0Rxr7SLjoR+B6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
The comments of TidRangeEval saids:
```
Returns false if we detect the range cannot contain any tuples.
```
After narrowing the upper and lower bounds, we can add an
additional check to verify if the lower bound exceeds the
upper bound. If true, return false to avoid unnecessary calls
to table_beginscan_tidrange.
PFA the trivial patch.
--
Regards
Junwang Zhao
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-add-a-bound-check-to-TidRangeEval.patch | application/octet-stream | 865 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2025-06-08 10:52:47 | Re: Support tid range scan in parallel? |
| Previous Message | Etsuro Fujita | 2025-06-08 08:45:23 | Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable |