From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: abhiroj95@gmail.com
Subject: BUG #17110: [FEATURE REQUEST] Log all plans for a query instead of just showing the most optimal plan
Date: Thu, 15 Jul 2021 11:58:12 +0000
Message-ID: <17110-55d0c019f99b8c13@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17110
Logged by: masterskipper
Email address: abhiroj95@gmail.com
PostgreSQL version: 11.10
Operating system: debian9
Description:
Hi,
Recently, we had to optimize a query that was behaving differently on
different databases (because data distribution and selectivity on each DB
were different). The problem is that it is very very difficult today to
understand why is the DB selecting the query plan it shows (and not other
plans). For e.g. why prefer sequential scan over index scan? what were the
costs that it calculated which made it prefer sequential scan?
Investigating such issues will become way more user friendly rather than
doing a guess work in and out. I believe this is a valid request and would
request you to please consider some time to fix it.
Many Thanks,
Abhiroj
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-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, abhiroj95@gmail.com
Subject: Re: BUG #17110: [FEATURE REQUEST] Log all plans for a query instead of just showing the most optimal plan
In-Reply-To: <17110-55d0c019f99b8c13@postgresql.org>
* 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