postgres-github.git / summary / log / commit / refs

commit    2d3490dd99f04d97202eb37f103f929f3dc33162
Author:   Peter Geoghegan <pg@bowt.ie>
Date:     Sat Apr 04 17:49:37 2026 +0000

    heapam: Keep buffer pins across index scan resets.
    
    Avoid dropping the heap page pin (xs_cbuf) and visibility map pin
    (xs_vmbuffer) within heapam_index_fetch_reset.  Retaining these pins
    saves cycles during certain nested loop joins and merge joins that
    frequently restore a saved mark: cases where the next tuple fetched
    after a reset often falls on the same heap page will now avoid the cost
    of repeated pinning and unpinning.
    
    Avoiding dropping the scan's heap page buffer pin is preparation for an
    upcoming patch that will add I/O prefetching to index scans.  Testing of
    that patch (which makes heapam tend to pin more buffers concurrently
    than was typical before now) shows that the aforementioned cases get a
    small but clearly measurable benefit from this optimization.
    
    Upcoming work to add a slot-based table AM interface for index scans
    (which is further preparation for prefetching) will move VM checks for
    index-only scans out of the executor and into heapam.  That will expand
    the role of xs_vmbuffer to include VM lookups for index-only scans (the
    field won't just be used for setting pages all-visible during on-access
    pruning via the enhancement recently introduced by commit b46e1e54).
    Avoiding dropping the xs_vmbuffer pin will preserve the historical
    behavior of nodeIndexonlyscan.c, which always kept this pin on a rescan;
    that aspect of this commit isn't really new.
    
    Author: Peter Geoghegan <pg@bowt.ie>
    Reviewed-By: Andres Freund <andres@anarazel.de>
    Discussion: https://postgr.es/m/CAH2-Wz=g=JTSyDB4UtB5su2ZcvsS7VbP+ZMvvaG6ABoCb+s8Lw@mail.gmail.com

[parent: fda530013282]