| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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-05 23:26:14 |
| Message-ID: | CAApHDvrefg6=OniHCAzKN6qtW-oA4ZkKHysLF0rY6miiCrCHvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 6 Oct 2024 at 08:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
I didn't notice that any of these remained. I agree we should get rid
of it. The patch looks fine to me.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2024-10-06 03:29:58 | Re: Eager aggregation, take 3 |
| Previous Message | David Rowley | 2024-10-05 23:22:16 | Re: On disable_cost |