aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_clause.c
diff options
context:
space:
mode:
authorAndrew Dunstan <andrew@dunslane.net>2024-03-10 23:10:14 -0400
committerAndrew Dunstan <andrew@dunslane.net>2024-04-04 06:46:40 -0400
commit3311ea86edc7a689614bad754e17371865cdc11f (patch)
tree7c9d55385afb9b21a8c790a64b1b9ea8eedff90e /src/backend/parser/parse_clause.c
parent585df02b445f63167f145685e045e5b6074a5a30 (diff)
downloadpostgresql-3311ea86edc7a689614bad754e17371865cdc11f.tar.gz
postgresql-3311ea86edc7a689614bad754e17371865cdc11f.zip
Introduce a non-recursive JSON parser
This parser uses an explicit prediction stack, unlike the present recursive descent parser where the parser state is represented on the call stack. This difference makes the new parser suitable for use in incremental parsing of huge JSON documents that cannot be conveniently handled piece-wise by the recursive descent parser. One potential use for this will be in parsing large backup manifests associated with incremental backups. Because this parser is somewhat slower than the recursive descent parser, it is not replacing that parser, but is an additional parser available to callers. For testing purposes, if the build is done with -DFORCE_JSON_PSTACK, all JSON parsing is done with the non-recursive parser, in which case only trivial regression differences in error messages should be observed. Author: Andrew Dunstan Reviewed-By: Jacob Champion Discussion: https://postgr.es/m/7b0a51d6-0d9d-7366-3a1a-f74397a02f55@dunslane.net
Diffstat (limited to 'src/backend/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions