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: | 2024-12-16 07:39:06 |
Message-ID: | 255fe972-dea4-4d9d-b68e-705f032d72c8@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02.12.24 10:46, Peter Eisentraut wrote:
> This patch series changes several parsers in the backend and contrib
> modules to use bison pure parsers and flex reentrant scanners. This is
> ultimately toward thread-safety, but I think it's also just nicer in
> general, and it might also fix a few possible small memory leaks.
I did a bit more work on this, so here is an updated patch set.
> Not done yet:
> * src/backend/utils/misc/guc-file.l
> * src/pl/plpgsql/src/pl_gram.y
I converted both of these scanners to reentrant, but I haven't done the
plpgsql parser yet.
> Not relevant for backend thread-safety:
> * src/backend/bootstrap/
>
> It might make sense to eventually covert that one as well, just so that
> the APIs are kept similar. But that could be for later.
I have done this one.
I'll leave it at this for now and wait for some reviews.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Lakhin | 2024-12-16 08:00:00 | Re: Visibility bug with prepared transaction with subtransactions on standby |
Previous Message | jian he | 2024-12-16 07:07:51 | using index to speedup add not null constraints to a table |