Re: GIN improvements part2: fast scan
От | Heikki Linnakangas |
---|---|
Тема | Re: GIN improvements part2: fast scan |
Дата | |
Msg-id | 51C16235.3080308@vmware.com обсуждение исходный текст |
Ответ на | Re: GIN improvements part2: fast scan (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: GIN improvements part2: fast scan
|
Список | pgsql-hackers |
On 18.06.2013 23:59, Alexander Korotkov wrote: > I would like to illustrate that on example. Imagine you have fulltext query > "rare_term& frequent_term". Frequent term has large posting tree while > rare term has only small posting list containing iptr1, iptr2 and iptr3. At > first we get iptr1 from posting list of rare term, then we would like to > check whether we have to scan part of frequent term posting tree where iptr > < iptr1. So we call pre_consistent([false, true]), because we know that > rare term is not present for iptr< iptr2. pre_consistent returns false. So > we can start scanning frequent term posting tree from iptr1. Similarly we > can skip lags between iptr1 and iptr2, iptr2 and iptr3, from iptr3 to > maximum possible pointer. Thanks, now I understand the rare-term & frequent-term problem. Couldn't you do that with the existing consistent function? I don't see why you need the new pre-consistent function for this. - Heikki
В списке pgsql-hackers по дате отправления: