Re: WIP Incremental JSON Parser

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: WIP Incremental JSON Parser
Date: 2024-03-25 23:27:46
Message-ID: CAOYmi+n4SeMsynrt=mYR=BNgR6aHzBWo3rpV4fMy0jsRXftPWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 25, 2024 at 4:24 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> OK, so we invent a new error code and have the parser return that if the stack depth gets too big?

Yeah, that seems reasonable. I'd potentially be able to build on that
via OAuth for next cycle, too, since that client needs to limit its
memory usage.

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-03-25 23:43:08 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Andrew Dunstan 2024-03-25 23:24:08 Re: WIP Incremental JSON Parser