Re: On disable_cost

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Alena Rybakina <a.rybakina@postgrespro.ru>, David Rowley <dgrowleyml@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Heikki Linnakangas <hlinnaka@iki.fi>, Peter Geoghegan <pg@bowt.ie>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-10-05T19:35:49Z

Lists: pgsql-hackers

Attachments

fully-remove-disable_cost.patch (text/x-diff) patch

BTW, getting off the question of EXPLAIN output for a moment,
I don't understand why disable_cost is still a thing.  The
one remaining usage seems trivial to replace, as attached.

			regards, tom lane

Commits

Doc: add detail about EXPLAIN's "Disabled" property
- 84b8fccbe5c2 18.0 landed
Adjust EXPLAIN's output for disabled nodes
- 161320b4b960 18.0 landed
Fix order of parameters in a cost_sort call
- 87b6c3c0b703 18.0 landed
Show number of disabled nodes in EXPLAIN ANALYZE output.
- c01743aa4866 18.0 landed
Treat number of disabled nodes in a path as a separate cost metric.
- e22253467942 18.0 landed
Remove grotty use of disable_cost for TID scan plans.
- e4326fbc60c4 18.0 landed