Re: jsonb crash

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <drowley(at)postgresql(dot)org>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb crash
Date: 2021-09-29 20:48:03
Message-ID: CAApHDvo6XS8Gxs1JMROPdAX8MTe=FWCesH5Y+jzGZD3ADawsnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 30 Sept 2021 at 09:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> After further inspection, "what are we doing in jsonb_hash?" is
> indeed a relevant question, but it seems like it's a type mismatch
> not a nullness issue. EXPLAIN VERBOSE shows

I think you're right here. It should be hashing text. That seems to
be going wrong in check_memoizable() because it assumes it's always
fine to use the left side's type of the OpExpr to figure out the hash
function to use.

Maybe we can cache the left and the right type's hash function and use
the correct one in paraminfo_get_equal_hashops().

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2021-09-29 20:55:22 Re: DELETE CASCADE
Previous Message Melanie Plageman 2021-09-29 20:46:07 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)