Re: pg_parse_json() should not leak token copies on failure

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Subject: Re: pg_parse_json() should not leak token copies on failure
Date: 2024-10-31 21:10:14
Message-ID: CAOYmi+nVD=osxGuhev9QzJ=9uqODAW7ro+VAw0nSG5heK4S1kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 7, 2024 at 3:45 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> I've added a 0002 as well.

0002 has since been applied [1] so I'm reattaching v4-0001 to get the
cfbot happy again.

--Jacob

[1] https://git.postgresql.org/cgit/postgresql.git/commit/?id=41b023946d

Attachment Content-Type Size
v4-0001-jsonapi-add-lexer-option-to-keep-token-ownership.patch application/octet-stream 17.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-10-31 21:24:36 Re: In-placre persistance change of a relation
Previous Message David E. Wheeler 2024-10-31 20:12:44 Re: RFC: Extension Packaging & Lookup