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 11:59:39
Message-ID: 202405101159.ttkbzrb5l7vn@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2024-May-09, Michael Paquier wrote:

> Fix overread in JSON parsing errors for incomplete byte sequences

I'm getting this error in the new test:

t/002_inline.pl ........................ 1/?
# Failed test 'incomplete UTF-8 sequence, chunk size 3: correct error output'
# at t/002_inline.pl line 134.
# 'Escape sequence "\�1+2" is invalid.'
# doesn't match '(?^:(Token|Escape sequence) ""?\\\x{F5}" is invalid)'
# Looks like you failed 1 test of 850.

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

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Every machine is a smoke machine if you operate it wrong enough."
https://twitter.com/libseybieda/status/1541673325781196801

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2024-05-10 12:23:09 Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence
Previous Message Tom Lane 2024-05-09 22:56:56 pgsql: Doc: update the "Using EXPLAIN" examples to match current code.

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Borisov 2024-05-10 12:10:04 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Previous Message Alena Rybakina 2024-05-10 11:49:56 Re: Fix parallel vacuum buffer usage reporting