Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Ankit Kumar Pandey <itsankitkp(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pghackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Date: 2023-01-03 03:08:36
Message-ID: CAApHDvpBQs=QdqZHW5iVMbdNSkp4zBHHnXYZz6dFagaJHs_3Tw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 26 Dec 2022 at 08:05, Ankit Kumar Pandey <itsankitkp(at)gmail(dot)com> wrote:
> Also, inputs from other hackers are welcomed here.

I'm with Tom on this. I've never once used this feature to try to
figure out why a certain plan was chosen or not chosen.

Do you actually have a need for this or are you just trying to tick
off some TODO items?

I'd really rather not see us compiling all that debug code in by
default unless it's actually going to be useful to a meaningful number
of people.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-01-03 03:11:46 RADIUS tests and improvements
Previous Message David Rowley 2023-01-03 02:51:36 Re: Todo: Teach planner to evaluate multiple windows in the optimal order