On Fri, Jan 03, 2020 at 09:33:35AM -0500, Jeff Janes wrote:
> Of course this doesn't really answer your question, as the
> separately-reported costs of a bitmap heap and bitmap index scan are
> unlikely to match what the costs would be of a regular index scan, if they
> were reported separately.
I
On Fri, Jan 3, 2020 at 9:14 AM Justin Pryzby wrote:
> Is it possible to tell what component of the cost estimate of an index
> scan is
> from the index reads vs heap ?
>
Not that I have found, other than through sprinkling elog statements
throughout the costing code. Which is horrible, because
Is it possible to tell what component of the cost estimate of an index scan is
from the index reads vs heap ?
It would help to be able to set enable_bitmapscan=FORCE (to make all index
scans go through a bitmap). Adding OR conditions can sometimes do this. That
includes cost of bitmap manipulati
