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

On 25/12/22 23:54, Tom Lane wrote:
>
> These days people
> would probably also wish that the output could be machine-
> readable in some way (JSON-formatted, perhaps).

Perhaps switch to enable logs could be on (standard logging style),
json, xml etc and print the output

as required?

> however, because it won't show you anything about
> paths that were considered and immediately rejected by
> add_path (or never got to add_path at all, because of the
> approximate-initial-cost filters in joinpath.c). We've
> sometimes speculated about logging every path submitted to
> add_path, but that would likely be too verbose to be very
> helpful.
>
Maybe we could add verbose option too and this could be one of the
output. Are there any more relevant information

that you could think of which can be included here?

Also, inputs from other hackers are welcomed here.

--
Regards,
Ankit Kumar Pandey