Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Subject: Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence
Date: 2024-05-13 03:22:02
Message-ID: ZkGHWhUT-fW0459n@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, May 10, 2024 at 02:23:09PM +0200, Alvaro Herrera wrote:
> Ah, I ran 'git clean -dfx' and now it works correctly. I must have had
> an incomplete rebuild.

I am going to assume that this is an incorrect build. It seems to me
that src/common/ was compiled with a past version not sufficient to
make the new test pass as more bytes got pushed to the error output as
the pre-855517307db8 code could point to some random junk.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2024-05-13 08:35:11 pgsql: Fix test case to do what it intends to
Previous Message Alexander Korotkov 2024-05-12 21:00:38 pgsql: Add permission check for MERGE/SPLIT partition operations

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Jungwirth 2024-05-13 04:54:34 Re: SQL:2011 application time
Previous Message Alexander Korotkov 2024-05-13 01:42:20 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.