Re: jsonb crash
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Jaime Casanova <jcasanov@systemguards.com.ec>,
Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-11-08T01:46:03Z
Lists: pgsql-hackers
On Sat, 6 Nov 2021 at 11:38, Justin Pryzby <pryzby@telsasoft.com> wrote: > > On Tue, Oct 26, 2021 at 07:07:01PM +1300, David Rowley wrote: > > Does anyone have any thoughts on the proposed fixes? > > I don't have any thoughts, but I want to be sure it isn't forgotten. Not forgotten. I was just hoping to get some feedback. I've now pushed the fix to restrict v14 to only allow Memoize when the left and right types are the same. For master, since it's possible to add a field to RestrictInfo, I've changed that to cache the left and right hash equality operators. This does not fix the binary / logical issue mentioned by Tom. I have ideas about allowing Memoize to operate in a binary equality mode or logical equality mode. I'll need to run in binary mode when there are lateral vars or when any join operator is not hashable. David
Commits
-
Allow Memoize to operate in binary comparison mode
- 6c32c0977783 14.2 landed
- e502150f7d0b 15.0 landed
-
Fix incorrect hash equality operator bug in Memoize
- 1f194ed6c26e 14.1 landed
- 39a3105678a2 15.0 landed