Re: pure parsers and reentrant scanners

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pure parsers and reentrant scanners
Date: 2025-01-24 06:46:48
Message-ID: 4a206335-05a2-4701-9151-508e0faf6836@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17.01.25 16:40, Peter Eisentraut wrote:
> 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.

This has been committed.

I think this concludes this topic.

For those who haven't seen it, I wrote a blog post about this:
https://peter.eisentraut.org/blog/2025/01/21/implementing-thread-safe-scanners-and-parsers-in-postgresql

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-01-24 07:32:45 Re: POC: track vacuum/analyze cumulative time per relation
Previous Message Michael Paquier 2025-01-24 06:44:06 Re: Improve verification of recovery_target_timeline GUC.