On Thu, May 16, 2024 at 11:50:20AM -0400, Andrew Dunstan wrote: > > Maybe "Introduce an incremental JSON parser" would have been a better > > > headline. > > Well, this gets into a level of detail that is beyond the average > > reader. I think at that level people will need to read the git logs or > > review the code. Do we use it for anything yet? > > > Yes, certainly, it's used in handling backup manifests. Without it we can't > handle huge manifests. See commits ea7b4e9a2a and 222e11a10a. > > Other uses are in the works.
Okay, added in the attached applied patch. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml index 428cb5c5a2e..9c511848943 100644 --- a/doc/src/sgml/release-17.sgml +++ b/doc/src/sgml/release-17.sgml @@ -2451,6 +2451,17 @@ User-defined data type receive functions will no longer receive their data null- </para> </listitem> +<!-- +Author: Andrew Dunstan <and...@dunslane.net> +2024-04-04 [3311ea86e] Introduce a non-recursive JSON parser +--> + +<listitem> +<para> +Add incremental JSON parser for use with huge JSON documents (Andrew Dunstan) +</para> +</listitem> + <!-- Author: Nathan Bossart <nat...@postgresql.org> 2024-02-28 [363eb0599] Convert README to Markdown.
