Horton

Re: On disable_cost

David Rowley <dgrowleyml@gmail.com>

View thread View on postgr.es
From: David Rowley <dgrowleyml@gmail.com>
To: Alena Rybakina <a.rybakina@postgrespro.ru>
Cc: Robert Haas <robertmhaas@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnaka@iki.fi>, Peter Geoghegan <pg@bowt.ie>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-10-11T04:24:14Z
Lists: pgsql-hackers 
On Fri, 11 Oct 2024 at 02:02, Alena Rybakina <a.rybakina@postgrespro.ru> wrote:
> On 10.10.2024 15:43, David Rowley wrote:
>
> > If anyone wants to take a look at the attached, please do so.
> > Otherwise, I'm pretty happy with it and will likely push it on New
> > Zealand Friday (aka later today).
>
> I think you missed some previous output and we should fix that.

Thanks. I should install ICU...

I've now pushed this change and will look at the docs now.

David

Commits

  1. Doc: add detail about EXPLAIN's "Disabled" property

  2. Adjust EXPLAIN's output for disabled nodes

  3. Fix order of parameters in a cost_sort call

  4. Show number of disabled nodes in EXPLAIN ANALYZE output.

  5. Treat number of disabled nodes in a path as a separate cost metric.

  6. Remove grotty use of disable_cost for TID scan plans.