Re: pure parsers and reentrant scanners
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-01-17T15:40:54Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Return yyparse() result not via global variable
- 473a575e0597 18.0 landed
-
Remove flex version checks
- 0869ea43e9c2 18.0 landed
-
Drop warning-free support for Flex 2.5.35
- 6fdd5d956343 18.0 landed
-
plpgsql: pure parser and reentrant scanner
- 7b27f5fd36cb 18.0 landed
-
flex code modernization: Replace YY_EXTRA_TYPE define with flex option
- b1ef48980ddd 18.0 landed
-
guc: reentrant scanner
- d663f150b5ed 18.0 landed
-
jsonpath scanner: reentrant scanner
- 2a7425d7eef9 18.0 landed
-
syncrep parser: pure parser and reentrant scanner
- db6856c9913f 18.0 landed
-
replication parser: pure parser and reentrant scanner
- e4a8fb8fefb9 18.0 landed
-
bootstrap: pure parser and reentrant scanner
- 3e4bacb17100 18.0 landed
-
Small whitespace improvement
- 399d0f1e11b5 18.0 landed
-
Prevent redeclaration of typedef yyscan_t
- 382092a0cd2c 18.0 landed
-
seg: pure parser and reentrant scanner
- 1f0de66ea2a5 18.0 landed
-
cube: pure parser and reentrant scanner
- 802fe923e3cd 18.0 landed
Attachments
- 0001-plpgsql-Return-parse-result-not-via-global-variable.patch (text/plain) patch 0001
- 0002-pgbench-Return-parse-result-not-via-global-variable.patch (text/plain) patch 0002
- 0003-replication-parser-Return-parse-result-not-via-globa.patch (text/plain) patch 0003
- 0004-syncrep-parser-Return-parse-result-not-via-global-va.patch (text/plain) patch 0004
Here are some more patches. This should cover the last sub-topic of this topic: not passing the yyparse() result via global variables. This uses techniques that are already in use in some parsers in the tree, for example cube and jsonpath. The syncrep parser was a bit trickier, because there we need to pass the syncrep_parse_error variable all the way down to the scanner (not just the parser), but overall it's all still pretty compact and standard.