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

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
Subject: Re: What to call an executor node which lazily caches tuples in a hash table? (GUC)
Date: 2021-06-03 02:36:19
Message-ID: 20210603023619.GC14099@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-06-03 02:38:07 Re: A micro-optimisation for ProcSendSignal()
Previous Message Thomas Munro 2021-06-03 02:07:02 Re: Outdated comments about proc->sem in lwlock.c