Re: Chaotically weird execution plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Chaotically weird execution plan
Date
Msg-id 17643.1222225270@sss.pgh.pa.us
Whole thread Raw
In response to Re: Chaotically weird execution plan  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: Chaotically weird execution plan  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-performance
Craig Ringer <craig@postnewspapers.com.au> writes:
> I'd already written: "If you need the test for status = 1, consider a
> partial index" when I noticed your schema definition:

>> "comments_created_by" btree (created_by) WHERE status = 1

> I find it hard to guess why it's having to recheck the WHERE clause
> given the use of a partial index that should cover that nicely.

No, that's operating as designed.  A bitmap scan's RECHECK condition
is only applied when the bitmap has become lossy due to memory
pressure.  In that case we have to look at each row on each of the pages
fingered by the index as containing possible matches ... and we'd better
check the partial-index qual too, since maybe not all the rows on those
pages will satisfy it.  In a plain indexscan there is no lossiness
involved and so the partial-index qual need never be rechecked.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Chaotically weird execution plan
Next
From: Craig Ringer
Date:
Subject: Re: Chaotically weird execution plan