From 866e6e1d04d4ae9615bd1899a757dae0191e9c77 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Sat, 10 May 2014 23:24:23 +0300 Subject: [PATCH] Fix bug in lossy-page handling in GIN When returning rows from a bitmap, as done with partial match queries, we would get stuck in an infinite loop if the bitmap contained a lossy page reference. This bug is new in master, it was introduced by the patch to allow skipping items refuted by other entries in GIN scans. Report and fix by Alexander Korotkov --- src/backend/access/gin/ginget.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/backend/access/gin/ginget.c b/src/backend/access/gin/ginget.c index 271f09901b9..144ed504dc2 100644 --- a/src/backend/access/gin/ginget.c +++ b/src/backend/access/gin/ginget.c @@ -741,7 +741,9 @@ entryGetItem(GinState *ginstate, GinScanEntry entry, while (entry->matchResult == NULL || (entry->matchResult->ntuples >= 0 && entry->offset >= entry->matchResult->ntuples) || - entry->matchResult->blockno < advancePastBlk) + entry->matchResult->blockno < advancePastBlk || + (ItemPointerIsLossyPage(&advancePast) && + entry->matchResult->blockno == advancePastBlk)) { entry->matchResult = tbm_iterate(entry->matchIterator);