| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, 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-29 07:04:26 |
| Message-ID: | 849f656f3d20976c95d669ca3e4ef010a124ab93.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2024-10-29 at 12:21 +1300, David Rowley wrote:
> When using the enable/disable flags to disable plan node types, many of
> the flags only discourage the use of the corresponding plan node and don't
> outright disallow the planner's ability to use the plan node type. This
> is by design so that the planner still maintains the ability to form a
> plan for a given query. When the resulting plan contains a disabled node,
> the <command>EXPLAIN</command> output will indicate this fact.
That patch is good in my opinion.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-10-29 07:16:42 | Re: proposal: schema variables |
| Previous Message | Michael Paquier | 2024-10-29 06:51:11 | Re: -Wformat-signedness |