NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit866e6e1

committed

Fix bug in lossy-page handling in GIN

When returning rows from a bitmap, as done with partial match queries, wewould get stuck in an infinite loop if the bitmap contained a lossy pagereference.This bug is new in master, it was introduced by the patch to allow skippingitems refuted by other entries in GIN scans.Report and fix by Alexander Korotkov

1 parenteaba54c commit866e6e1Copy full SHA for 866e6e1

File tree

1 file changed

-1

lines changed

src/backend/access/gin
- ginget.c

1 file changed

-1

lines changed

`‎src/backend/access/gin/ginget.c`

Lines changed: 3 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -741,7 +741,9 @@ entryGetItem(GinState *ginstate, GinScanEntry entry,`
`741`	`741`	`while (entry->matchResult==NULL\|\|`
`742`	`742`	`(entry->matchResult->ntuples >=0&&`
`743`	`743`	`entry->offset >=entry->matchResult->ntuples)\|\|`
`744`		`-entry->matchResult->blockno<advancePastBlk)`
	`744`	`+entry->matchResult->blockno<advancePastBlk\|\|`
	`745`	`+ (ItemPointerIsLossyPage(&advancePast)&&`
	`746`	`+entry->matchResult->blockno==advancePastBlk))`
`745`	`747`	`{`
`746`	`748`	`entry->matchResult=tbm_iterate(entry->matchIterator);`
`747`	`749`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit866e6e1

File tree

1 file changed

1 file changed

`‎src/backend/access/gin/ginget.c`

0 commit comments