pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
distinguish index cost component from table component 3+ messages / 2 participants [nested] [flat]
* distinguish index cost component from table component @ 2020-01-03 14:14 Justin Pryzby <pryzby@telsasoft.com> 0 siblings, 1 reply; 3+ messages in thread From: Justin Pryzby @ 2020-01-03 14:14 UTC (permalink / raw) To: 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. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: distinguish index cost component from table component @ 2020-01-03 14:33 Jeff Janes <jeff.janes@gmail.com> parent: Justin Pryzby <pryzby@telsasoft.com> 0 siblings, 1 reply; 3+ messages in thread From: Jeff Janes @ 2020-01-03 14:33 UTC (permalink / raw) To: Justin Pryzby <pryzby@telsasoft.com>; +Cc: pgsql-performance On Fri, Jan 3, 2020 at 9:14 AM Justin Pryzby <pryzby@telsasoft.com> 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 then you get estimates for all the considered but rejected index scans as well, but without the context to know what they are for. So it only works for toy queries where there are few possible indexes to consider. It would help to be able to set enable_bitmapscan=FORCE (to make all index > scans go through a bitmap). Doesn't enable_indexscan=off accomplish this already? It is possible but not terribly likely to switch from index to seq, rather than from index to bitmap. (Unless the index scan was being used to obtain an ordered result, but a hypothetical enable_bitmapscan=FORCE can't fix that). 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. Or maybe explain should report it. > I wouldn't be optimistic about getting such a backwards-incompatible change accepted (plus it would surely add some small accounting overhead, which again would probably not be acceptable). But if you do enough tuning work, perhaps it would be worth carrying an out-of-tree patch to implement that. I wouldn't be so interested in writing such a patch, but would be interested in using one were it available somewhere. Cheers, Jeff ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: distinguish index cost component from table component @ 2020-01-03 16:03 Justin Pryzby <pryzby@telsasoft.com> parent: Jeff Janes <jeff.janes@gmail.com> 0 siblings, 0 replies; 3+ messages in thread From: Justin Pryzby @ 2020-01-03 16:03 UTC (permalink / raw) To: Jeff Janes <jeff.janes@gmail.com>; +Cc: pgsql-performance 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 think the cost of index component of bitmap scan would be exactly the same as the cost of the original indexscan. >> Or maybe explain should report it. > > I wouldn't be optimistic about getting such a backwards-incompatible change > accepted (plus it would surely add some small accounting overhead, which > again would probably not be acceptable). But if you do enough tuning work, > perhaps it would be worth carrying an out-of-tree patch to implement that. > I wouldn't be so interested in writing such a patch, but would be > interested in using one were it available somewhere. I did the attached in the simplest possible way. If it's somehow possible get the path's index_total_cost from the plan, then there'd be no additional overhead. Justin Attachments: [text/x-diff] v1-0001-explain-show-index_total_cost.patch (0B, ../../20200103160315.GL12066@telsasoft.com/2-v1-0001-explain-show-index_total_cost.patch) download ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-01-03 16:03 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-01-03 14:14 distinguish index cost component from table component Justin Pryzby <pryzby@telsasoft.com> 2020-01-03 14:33 ` Jeff Janes <jeff.janes@gmail.com> 2020-01-03 16:03 ` Justin Pryzby <pryzby@telsasoft.com>
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