Re: WIP Incremental JSON Parser
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Smith <smithpb2250@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-02-27T05:20:42Z
Lists: pgsql-hackers
On 2024-02-26 Mo 19:20, Andrew Dunstan wrote: > > On 2024-02-26 Mo 10:10, Jacob Champion wrote: >> On Mon, Feb 26, 2024 at 7:08 AM Jacob Champion >> <jacob.champion@enterprisedb.com> wrote: >>> As a brute force example of the latter, with the attached diff I get >>> test failures at chunk sizes 1, 2, 3, 4, 6, and 12. >> But this time with the diff. >> > > Ouch. I'll check it out. Thanks! > > > The good news is that the parser is doing fine - this issue was due to a thinko on my part in the test program that got triggered by the input file size being an exact multiple of the chunk size. I'll have a new patch set later this week. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Post review fixes for test_json_parser test module
- ba3e6e2bca97 17.0 landed
-
Shrink test file for test_json_parser module
- b8a7bfa33324 17.0 landed
-
Add support for incrementally parsing backup manifests
- ea7b4e9a2a7c 17.0 landed
-
Introduce a non-recursive JSON parser
- 3311ea86edc7 17.0 landed
-
Use incremental parsing of backup manifests.
- 222e11a10ae9 17.0 landed