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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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-15 00:00:01
Message-ID: ZkP7ARo6lo90su3K@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, May 14, 2024 at 10:39:36AM +0200, Peter Eisentraut wrote:
> I saw the same thing. The problem is that there is incomplete dependency
> information in the makefiles (not meson) between src/common/ and what is
> using it. So whenever anything changes in src/common/, you pretty much have
> to do a forced rebuild of everything.

Is that a recent regression? I have some blurry memories from
working on these areas that changing src/common/ reflected on the
compiled pieces effectively at some point.
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2024-05-15 00:19:37 pgsql: Fix handling of polymorphic output arguments for procedures.
Previous Message Tom Lane 2024-05-14 20:46:44 pgsql: Do pre-release housekeeping on catalog data.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2024-05-15 00:02:03 Re: Row pattern recognition
Previous Message Thomas Munro 2024-05-14 22:26:43 Re: Why is citext/regress failing on hamerkop?