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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 24, 2015 at 2:40 PM, Laurent Debacker <debackerl@xxxxxxxxx> 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


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux