Re: On disable_cost - Mailing list pgsql-hackers

From Robert Haas
Subject Re: On disable_cost
Date
Msg-id CA+Tgmoap+RnLKSDoaVauR1ZGo+zFBsGSFQQUzE2cEQdmbS8iaA@mail.gmail.com
Whole thread Raw
In response to On disable_cost  (Zhenghua Lyu <zlv@pivotal.io>)
Responses Re: On disable_cost
Re: On disable_cost
List pgsql-hackers
On Thu, Oct 3, 2024 at 1:35 PM Alena Rybakina <a.rybakina@postgrespro.ru> wrote:
> I think you are right, most users will perceive this parameter as the number of rejected paths, and not in any other
way.
>
> To be honest, I don't have much experience writing documentation, but I think we should add a little more information
todoc/src/sgml/perform.sgml. 
>
> It contains a description about "explain queries", so the description of "Disabled nodes" is available there.
>
> I prepared a patch that includes the information we can add.

One general thing to think about is that we really document very
little about EXPLAIN. That might not be good, but we should consider
whether it will look strange if we document a bunch of stuff about
this and still don't talk about anything else.

(This is not a comment on this specific patch, which I have not
examined. It's just a general thought.)

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_walsummary, Character-not-present-in-option
Next
From: Masahiko Sawada
Date:
Subject: Re: Using per-transaction memory contexts for storing decoded tuples