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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-10 12:23:09
Message-ID: 202405101223.66lahv2qiwe7@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2024-May-10, Alvaro Herrera wrote:

> Not sure what's going on here, or why it fails for me while the
> buildfarm is all happy.

Ah, I ran 'git clean -dfx' and now it works correctly. I must have had
an incomplete rebuild.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"World domination is proceeding according to plan" (Andrew Morton)

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2024-05-10 13:11:26 pgsql: Fix ON CONFLICT DO NOTHING/UPDATE for temporal indexes
Previous Message Alvaro Herrera 2024-05-10 11:59:39 Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-05-10 12:48:07 Re: open items
Previous Message Pavel Borisov 2024-05-10 12:10:04 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.