pgsql: Check for interrupts and stack overflow in TParserGet(). - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Check for interrupts and stack overflow in TParserGet().
Date
Msg-id E1qDAeH-000FLa-5g@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Check for interrupts and stack overflow in TParserGet().

TParserGet() recurses for some token types, meaning it's possible
to drive it to stack overflow.  Since this is a minority behavior,
I chose to add the check_stack_depth() call to the two places that
recurse rather than doing it during every single call.

While at it, add CHECK_FOR_INTERRUPTS(), because this can run
unpleasantly long for long inputs.

Per bug #17995 from Zuming Jiang.  This is old, so back-patch
to all supported branches.

Discussion: https://postgr.es/m/17995-9f20ff3e6389db4c@postgresql.org

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/b6ab18a990ffd0daa55665e3153bfed9db547fa7

Modified Files
--------------
src/backend/tsearch/wparser_def.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Check for interrupts and stack overflow in TParserGet().
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Change "..." to cstring in old input/output function comments.