diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2024-04-07 00:24:12 +0200 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2024-04-07 00:24:14 +0200 |
| commit | 04e72ed617be354a53a076b76c6644e364ed80a3 (patch) | |
| tree | eee07b6e2234b211b393d09e8f6671c3a59b5b2d /src/backend/executor/nodeWindowAgg.c | |
| parent | 87c21bb9412c8ba2727dec5ebcd74d44c2232d11 (diff) | |
| download | postgresql-04e72ed617be354a53a076b76c6644e364ed80a3.tar.gz postgresql-04e72ed617be354a53a076b76c6644e364ed80a3.zip | |
BitmapHeapScan: Push skip_fetch optimization into table AM
Commit 7c70996ebf0949b142 introduced an optimization to allow bitmap
scans to operate like index-only scans by not fetching a block from the
heap if none of the underlying data is needed and the block is marked
all visible in the visibility map.
With the introduction of table AMs, a FIXME was added to this code
indicating that the skip_fetch logic should be pushed into the table
AM-specific code, as not all table AMs may use a visibility map in the
same way.
This commit resolves this FIXME for the current block. The layering
violation is still present in BitmapHeapScans's prefetching code, which
uses the visibility map to decide whether or not to prefetch a block.
However, this can be addressed independently.
Author: Melanie Plageman
Reviewed-by: Andres Freund, Heikki Linnakangas, Tomas Vondra, Mark Dilger
Discussion: https://postgr.es/m/CAAKRu_ZwCwWFeL_H3ia26bP2e7HiKLWt0ZmGXPVwPO6uXq0vaA%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeWindowAgg.c')
0 files changed, 0 insertions, 0 deletions