Re: On disable_cost

From: Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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 17:35:48
Message-ID: fe72b44d-ebd4-457f-8fe0-6a42ffe5bba9@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> Overall, I think we need to do something here. There's no
>> documentation about what Disabled Nodes means so we either need to
>> make it easier to understand without documenting it or add something
>> to the documents about it. If Laurenz, who has a huge amount of
>> PostgreSQL experience didn't catch it, then what hope is there for the
>> average user?
>
> 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.

--
Regards,
Alena Rybakina
Postgres Professional

Attachment Content-Type Size
0001-Documentation-about-Disabled-nodes.-We-need-to-descr.patch text/x-patch 2.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-10-03 18:24:01 Re: On disable_cost
Previous Message Robert Haas 2024-10-03 17:19:23 Re: pg_walsummary, Character-not-present-in-option