Re: bitmap heap scan recheck for gin/fts with no lossy blocks

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: bitmap heap scan recheck for gin/fts with no lossy blocks
Дата
Msg-id CAMkU=1x01Oway2SY3b_UKmVPFmarwN6MnK0WhSuwuS08KMudHw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: bitmap heap scan recheck for gin/fts with no lossy blocks  (Laurent Debacker <debackerl@gmail.com>)
Список pgsql-performance
Дерево обсуждения
On Fri, Jul 24, 2015 at 2:40 PM, Laurent Debacker <debackerl@gmail.com> wrote:


The Recheck Cond line is a plan-time piece of info, not a run-time piece.  It only tells you what condition is going to be rechecked if a recheck is found to be necessary.

Thanks Jeff! That makes sense indeed.

I'm a bit surprised a COUNT(1) would need a bitmap heap scan since we know the row count from the index, but okay.

Gin indexes do not (yet) implement index only scans.  It has to visit the block to check the visibility of the rows, as visibility data is not stored in the index.

Cheers,

Jeff

В списке pgsql-performance по дате отправления:

Предыдущее
От: Laurent Debacker
Дата:
Сообщение: Re: bitmap heap scan recheck for gin/fts with no lossy blocks
Следующее
От: Mark Kirkwood
Дата:
Сообщение: Re: hyperthreadin low performance