From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enable_resultcache confusion |
Date: | 2021-07-08 17:52:38 |
Message-ID: | CAKFQuwZQmCNyS_Vv2Jf3TNe7wRTiptWNs7xkgU=AEdqthkQe9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 8, 2021 at 10:29 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Jul 8, 2021 at 12:51 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Are we going to be forever explaining that enable_resultcache doesn't
> > cache query results?
>
> Yes, I can see that causing ongoing confusion. Naming things is really
> hard...
>
>
I agree that the chosen name is problematic. To borrow existing technical
nomenclature, what we seem to be doing here is adding "Node Memoization"
[1].
"enable_nodememoization" would work for me - by avoiding Result and using
Node the focus should remain without the bowels of the planner's plan and
not move to the output of the query as a whole. "Node Cache" would
probably work just as well if a wholesale change to Memoization doesn't
seem appealing, but the semantics of that term seem closer to what is
happening here.
The description in the commit message suggests we can use this for a wide
variety of nodes so adding any node specific typing to the name seems
unwise.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-07-08 18:00:12 | Re: enable_resultcache confusion |
Previous Message | Dean Rasheed | 2021-07-08 17:38:22 | Re: [PATCH] expand the units that pg_size_pretty supports on output |