On Fri, Jul 24, 2015 at 2:40 PM, Laurent Debacker
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
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.
Have a nice day,
Laurent
On Thu, Jul 23, 2015 at 8:04 PM, Jeff Janes wrote:
> On Thu, Jul 23, 2015 at 9:58 AM, Laurent Debacker
> wrote:
>
On Thu, Jul 23, 2015 at 9:58 AM, Laurent Debacker
wrote:
> Hi,
>
> I have read that GIN indexes don't require a recheck cond for full text
> search as long as work_mem is big enough, otherwise you get lossy blocks,
> and the recheck cond.
>
> In my case, I have no lossy blocks (from what I could
Hi,
I have read that GIN indexes don't require a recheck cond for full text
search as long as work_mem is big enough, otherwise you get lossy blocks,
and the recheck cond.
In my case, I have no lossy blocks (from what I could tell), but I do have
a recheck...
EXPLAIN (ANALYZE, BUFFERS) SELECT CO
