| From: | "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Chris Cleveland <ccleve+github(at)dieselpoint(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Look at all paths? |
| Date: | 2021-12-29 03:22:51 |
| Message-ID: | 4c162daf-4dab-5bd6-6cff-9a8512446219@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/29/21 5:07 AM, Chris Cleveland wrote:
> I'm developing a new index access method. Sometimes the planner uses it
> and sometimes it doesn't. I'm trying to debug the process to understand
> why the index does or doesn't get picked up.
>
> Is there a way to dump all of the query plans that the planner
> considered, along with information on why they were rejected? EXPLAIN
> only gives info on the plan that was actually selected.
You can enable OPTIMIZER_DEBUG option. Also the gdbpg code [1] makes our
work much easier, sometimes.
[1] https://github.com/tvondra/gdbpg
--
regards,
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-12-29 03:29:54 | Re: Documenting when to retry on serialization failure |
| Previous Message | tanghy.fnst@fujitsu.com | 2021-12-29 03:16:17 | RE: row filtering for logical replication |