Re: What to call an executor node which lazily caches tuples in a hash table? (GUC) - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: What to call an executor node which lazily caches tuples in a hash table? (GUC)
Date
Msg-id 20210603023619.GC14099@telsasoft.com
Whole thread Raw
In response to What to call an executor node which lazily caches tuples in a hash table?  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: What to call an executor node which lazily caches tuples in a hash table? (GUC)  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
You started the thread about what to call the node, but what about its GUC?

Should it be enable_result_cache instead of enable_resultcache?

See also Robert's opinion last year about enable_incrementalsort and "economizing on underscores".

https://www.postgresql.org/message-id/flat/CA%2BTgmoazhPwebpOwNbHt1vJoos1eLYhJVQPka%2BpptSLgS685aA%40mail.gmail.com#e6d5ea0a10384d540b924688c6357b21

-- 
Justin



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Outdated comments about proc->sem in lwlock.c
Next
From: Thomas Munro
Date:
Subject: Re: A micro-optimisation for ProcSendSignal()