Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays
James Coleman <jtc331@gmail.com>
From: James Coleman <jtc331@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-04-27T12:40:15Z
Lists: pgsql-hackers
On Sun, Apr 26, 2020 at 11:44 PM David Rowley <dgrowleyml@gmail.com> wrote: > > On Mon, 27 Apr 2020 at 15:12, James Coleman <jtc331@gmail.com> wrote: > > While working on this I noticed that dynahash.c line 499 has this assertion: > > > > Assert(info->entrysize >= info->keysize); > > > > Do you by any chance know why the entry would need to be larger than the key? > > Larger or equal. They'd be equal if you the key was the data, since > you do need to store at least the key. Looking at the code for > examples where dynahash is used in that situation, I see > _hash_finish_split(). Ah, I was thinking of it as key and value being separate sizes added together rather than one including the other. Thanks, James
Commits
-
Use a hash table to speed up NOT IN(values)
- 29f45e299e7f 15.0 landed
-
Speedup ScalarArrayOpExpr evaluation
- 50e17ad281b8 14.0 landed