Re: On disable_cost - Mailing list pgsql-hackers

From David Rowley
Subject Re: On disable_cost
Date
Msg-id CAApHDvoFF1VeqcZiQ0Y9aXwodz4-C+biVQbuW_CEkeuO5NJXDg@mail.gmail.com
Whole thread Raw
In response to Re: On disable_cost  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: On disable_cost
Re: On disable_cost
Re: On disable_cost
Re: On disable_cost
List pgsql-hackers
On Sat, 5 Oct 2024 at 03:03, Robert Haas <robertmhaas@gmail.com> wrote:
> I tend to gravitate
> toward displaying things exactly as they exist internally because I've
> had so many bad experiences with having to try to reverse-engineer the
> value stored internally from whatever is printed.

Thanks for explaining your point of view. I've not shifted my opinion
any, so I guess we just disagree. I feel a strong enough dislike for
the current EXPLAIN output to feel it's worth working harder to have a
better output.

I won't push my point any further unless someone else appears
supporting Laurenz and I. Thank you for working on getting rid of the
disabled_cost. I think what we have is now much better than before.
The EXPLAIN output is the only part I dislike about this work.

I'd encourage anyone else on the sidelines who has an opinion on how
to display the disabled-ness of a plan node in EXPLAIN to speak up
now, even if it's just a +1 to something someone has already written.
It would be nice to see what more people think.

David



pgsql-hackers by date:

Previous
From: Amul Sul
Date:
Subject: Re: New PostgreSQL Contributors
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: New PostgreSQL Contributors