Re: jsonb failed assertions

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: jsonb failed assertions
Date: 2014-05-28 19:50:04
Message-ID: 53863DEC.8000405@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/28/2014 04:13 AM, Peter Geoghegan wrote:
> On Wed, May 21, 2014 at 4:53 AM, Heikki Linnakangas
> <hlinnakangas(at)vmware(dot)com> wrote:
>> Hmm. The patch looks correct as far as it goes. But that function is still a
>> bit funny. When it compares two identical arrays (or objects), and reaches
>> the WJB_END_ARRAY token, it will still fall into the code that checks what
>> the va and vb types are, and compares the last scalar values in that array
>> again. That's wrong, and will fail if the compiler decides to clobber the
>> local "va" or "vb" variables between iterations of the do-while loop,
>> because JsonbIteratorNext() does not set the value when returning
>> WJB_END_ARRAY.
>
> That's an obsolete assumption that once actually applied during development.
>
> Attached revision also adds handling for that case.

Thanks, applied.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-05-28 19:55:16 Re: pg_stat directory and pg_stat_statements
Previous Message Tom Lane 2014-05-28 19:42:35 pgsql: Fix bogus %name-prefix option syntax in all our Bison files.