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-11 13:47:16
Message-ID: CAOYmi+n1dZEMCptykQS7Jd4A_bMyebAD9LuFXM4NaeaYKwH3ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 10, 2024 at 11:43 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I haven't managed to reproduce this. But I'm including some tests for it.

If I remove the newline from the end of the new tests:

> @@ -25,7 +25,7 @@ for (my $size = 64; $size > 0; $size--)
> foreach my $test_string (@inlinetests)
> {
> my ($fh, $fname) = tempfile();
> - print $fh "$test_string\n";
> + print $fh "$test_string";
> close($fh);
>
> foreach my $size (1..6, 10, 20, 30)

then I can reproduce the same result as my local tests. That extra
whitespace appears to help the partial token logic out somehow.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2024-03-11 14:03:35 Re: Adding OLD/NEW support to RETURNING
Previous Message Maxim Orlov 2024-03-11 13:43:49 Re: Add Index-level REINDEX with multiple jobs