Re: [PATCH] json_lex_string: don't overread on bad UTF8

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: [PATCH] json_lex_string: don't overread on bad UTF8
Date: 2024-05-09 17:21:00
Message-ID: CAOYmi+mnxN9y-Ht_hx2z3ex6OWOLJedU6cMJJAK15jggudUNCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 8, 2024 at 9:27 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> This is a bit mitigated by the fact that d6607016c738 is recent, but
> this is incorrect since v13 so backpatched down to that.

Thank you!

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2024-05-09 18:20:49 Re: request for database identifier in the startup packet
Previous Message Cary Huang 2024-05-09 17:16:32 Re: Support tid range scan in parallel?