Re: jsonb crash

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb crash
Date: 2021-11-08 01:46:03
Message-ID: CAApHDvoJ6pnZWMH9vhrewr0ZnCvM=3DGkrQ3pypdkcSO4nhOqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 6 Nov 2021 at 11:38, Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-11-08 02:35:12 Re: Commitfest 2021-11 Patch Triage - Part 1
Previous Message Kyotaro Horiguchi 2021-11-08 01:36:23 Re: Allow escape in application_name