From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | pgsql-hackers(at)postgresql(dot)org, David Rowley <drowley(at)postgresql(dot)org> |
Subject: | Re: jsonb crash |
Date: | 2021-09-29 20:30:54 |
Message-ID: | e996b9b3-e2ab-f75c-5ad6-29f4b71e36c8@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/29/21 4:00 PM, Tom Lane wrote:
> Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
>> I found a crash (segmentation fault) on jsonb.
>> This is the best I could do to reduce the query:
>> """
>> select
>> 75 as c1
>> from
>> public.pagg_tab_ml as ref_0,
>> lateral (select
>> ref_0.a as c5
>> from generate_series(1, 300) as sample_0
>> fetch first 78 rows only
>> ) as subq_0
>> where case when (subq_0.c5 < 2)
>> then cast(null as jsonb)
>> else cast(null as jsonb)
>> end ? ref_0.c
>> """
> I think this must be a memoize bug. AFAICS, nowhere in this query
> can we be processing a non-null JSONB value, so what are we doing
> in jsonb_hash? Something down-stack must have lost the information
> that the Datum is actually null.
Yeah, confirmed that this is not failing in release 13.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-09-29 20:33:52 | Re: prevent immature WAL streaming |
Previous Message | Tom Lane | 2021-09-29 20:24:03 | Re: jsonb crash |