summaryrefslogtreecommitdiff
path: root/src/include/nodes
diff options
context:
space:
mode:
authorMelanie Plageman2025-02-24 21:07:50 +0000
committerMelanie Plageman2025-02-24 21:10:13 +0000
commitb8778c4cd8bc924ce5347cb1ab10dfbf34130559 (patch)
treee04294273340adff516f244bc56550644b9f5d87 /src/include/nodes
parentc56e8af75e081383e05cf544f372506c8da4efe7 (diff)
Add lossy indicator to TBMIterateResult
TBMIterateResult->ntuples is -1 when the page in the bitmap is lossy. Add an explicit lossy indicator so that we can move ntuples out of the TBMIterateResult in a future commit. Discussion: https://postgr.es/m/CA%2BhUKGLHbKP3jwJ6_%2BhnGi37Pw3BD5j2amjV3oSk7j-KyCnY7Q%40mail.gmail.com
Diffstat (limited to 'src/include/nodes')
-rw-r--r--src/include/nodes/tidbitmap.h5
1 files changed, 3 insertions, 2 deletions
diff --git a/src/include/nodes/tidbitmap.h b/src/include/nodes/tidbitmap.h
index a6ffeac90be..8cd93d90a86 100644
--- a/src/include/nodes/tidbitmap.h
+++ b/src/include/nodes/tidbitmap.h
@@ -54,9 +54,10 @@ typedef struct TBMIterator
typedef struct TBMIterateResult
{
BlockNumber blockno; /* page number containing tuples */
- int ntuples; /* -1 indicates lossy result */
+ int ntuples; /* -1 when lossy */
+ bool lossy;
bool recheck; /* should the tuples be rechecked? */
- /* Note: recheck is always true if ntuples < 0 */
+ /* Note: recheck is always true if lossy */
OffsetNumber offsets[FLEXIBLE_ARRAY_MEMBER];
} TBMIterateResult;