distinguish index cost component from table component - Mailing list pgsql-performance

From Justin Pryzby
Subject distinguish index cost component from table component
Date
Msg-id 20200103141427.GK12066@telsasoft.com
Whole thread Raw
Responses Re: distinguish index cost component from table component  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-performance
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 manipulation, but it's good enough for me.

Or maybe explain should report it.



pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Merge join doesn't seem to break early when I (and planner) thinkit should - 10.4
Next
From: Jeff Janes
Date:
Subject: Re: distinguish index cost component from table component