Re: On disable_cost

On Sat, 12 Oct 2024 at 02:16, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Fri, 2024-10-11 at 20:45 +1300, David Rowley wrote:
> > + When using the enable/disable flags to disable plan node types, the
> > + majority of the flags only deprioritize the corresponding plan node
>
> I don't like "deprioritize".
> How about "discourage the use of"?

Yeah, that's ok for me.

> Besides, is that really the majority? I had though that only a few nodes
> are unavoidable (sequential scan, sort, nested loop). But I guess I am wrong.

Ok, I looked and you're right. I did make a quick pass to
approximately figure that out and I came up with:

Soft disable: enable_bitmapscan, enable_gathermerge, enable_hashagg,
enable_hashjoin, enable_indexscan, enable_mergejoin, enable_nestloop,
enable_seqscan, enable_sort

That's 9.

Hard disable: enable_async_append, enable_group_by_reordering,
enable_incremental_sort, enable_indexonlyscan, enable_material,
enable_memoize, enable_parallel_append, enable_parallel_hash,
enable_partition_pruning, enable_partitionwise_aggregate,
enable_partitionwise_join, enable_presorted_aggregate, enable_tidscan

And 13.

(there are a few ones that are in a grey area such as enable_hashagg
or enable_tidscan will still happen with a WHERE CURRENT OF <cursor>.)

I changed "majority" to "many"

> > + and don't outright disallow the planner's ability to use the plan node
> > + type. This is done so that the planner still maintains the ability to
> > + form a plan for a given query. Otherwise, certain queries would not be
> > + possible to execute when certain plan node types are disabled. This means
>
> "would not be possible to execute" can be simplified to "could be executed".

Changed.

> Can we have "sequential scan" instead of "Seq Scan"?
> It's somewhat unrelated, but I cannot count how many people I have talked
> to who think that it is a "sequence scan".

Yeah, looks like we only call it "Seq Scan" in EXPLAIN and we use
"sequence scan" when talking about it in sentences.

Thanks for looking. Updated patch is attached.

David