From: Justin Pryzby <pryzby@telsasoft.com>
To: pgsql-performance@postgresql.org
Subject: distinguish index cost component from table component
Date: Fri, 3 Jan 2020 08:14:27 -0600
Message-ID: <20200103141427.GK12066@telsasoft.com> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com
Subject: Re: distinguish index cost component from table component
In-Reply-To: <20200103141427.GK12066@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox