From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: On disable_cost |
Date: | 2024-10-03 18:24:01 |
Message-ID: | CA+Tgmoap+RnLKSDoaVauR1ZGo+zFBsGSFQQUzE2cEQdmbS8iaA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 3, 2024 at 1:35 PM Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)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 to doc/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
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2024-10-03 18:32:44 | Re: Using per-transaction memory contexts for storing decoded tuples |
Previous Message | Alena Rybakina | 2024-10-03 17:35:48 | Re: On disable_cost |