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

From David Rowley
Subject Re: What to call an executor node which lazily caches tuples in a hash table?
Date
Msg-id CAApHDvqh4TU2ZSSxtn-w9+UqrnqgyLWhNwuTWBXYM7Y98=WhYw@mail.gmail.com
Whole thread Raw
In response to Re: What to call an executor node which lazily caches tuples in a hash table?  (Andy Fan <zhihui.fan1213@gmail.com>)
List pgsql-hackers
On Wed, 31 Mar 2021 at 14:43, Andy Fan <zhihui.fan1213@gmail.com> wrote:
> When naming it,  we may also think about some non native English speakers, so
> some too advanced words may make them uncomfortable.  Actually when  I read
> "Reactive", I googled to find what its meaning is. I knew reactive programming, but I
> do not truly understand "reactive hash".

The origin of that idea came from "reactive" being the opposite of
"proactive". If that's not clear then it's likely a bad choice for a
name.

I had thought proactive would mean "do things beforehand" i.e not on
demand.  Basically, just fill the hash table with records that we need
to put in it rather than all records that we might need, the latter
being what Hash Join does, and the former is what the new node does.

David



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies
Next
From: Michael Paquier
Date:
Subject: Re: multi-install PostgresNode fails with older postgres versions