Re: Moving _bt_readpage and _bt_checkkeys into a new .c file
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-07T22:30:54Z
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 →
-
Avoid pointer chasing in _bt_readpage inner loop.
- 83a26ba59b18 19 (unreleased) landed
-
Relocate _bt_readpage and related functions.
- 65d6acbc5649 19 (unreleased) landed
-
Fix bug in nbtree array primitive scan scheduling.
- 763d65ae2545 18.0 cited
On Sat, Dec 6, 2025 at 9:44 PM Peter Geoghegan <pg@bowt.ie> wrote: > Since this ignore_killed_tuples change is also very simple, and also > seems like an easy win, I think that it can be committed as part of > the second patch. Without it needing to wait for too much more > performance validation. My plan is to commit the entire patch series (with a modified second patch that includes the ignore_killed_tuples change) in the next couple of days. As far as I can determine through performance validation that tested a variety of different scan types (simple point lookups, range scans, and a variety of different SAOP scan patterns), the patch series is an unambiguous win. It appears to be slightly faster even in unsympathetic cases, such as standard pgbench SELECT. -- Peter Geoghegan