Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_parse_json() should not leak token copies on failure - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: pg_parse_json() should not leak token copies on failure
Date
Msg-id CAOYmi+nRDX5HNHFg76w-4zjJ2TJHbVg6K1Xj2P64vV7v9-wxrQ@mail.gmail.com
Whole thread Raw
In response to pg_parse_json() should not leak token copies on failure  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: pg_parse_json() should not leak token copies on failure
List pgsql-hackers
Tree view 
On Tue, Apr 30, 2024 at 2:29 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> Attached is a draft patch to illustrate what I mean, but it's
> incomplete: it only solves the problem for scalar values.

(Attached is a v2 of that patch; in solving a frontend leak I should
probably not introduce a backend segfault.)

--Jacob
Attachment

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: Justin Pryzby
Date:
Subject: Re: warn if GUC set to an invalid shared library