pgsql: Handle operator-stack-overflow errors softly in tsquery and ltxt - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Handle operator-stack-overflow errors softly in tsquery and ltxt
Date
Msg-id E1xDodE-00000000SCK-1XRq@gemulon.postgresql.org
Whole thread
List pgsql-committers
Handle operator-stack-overflow errors softly in tsquery and ltxtquery.

When we converted these types' input functions to report errors
through the soft-error mechanism, we missed that stack-overflow
errors can be triggered through bad user input.  Convert those
to be reported softly, too.

Bug: #19745
Reported-by: Ke <kehan5800@gmail.com>
Author: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/19745-39cd7b93a505f9a9@postgresql.org
Backpatch-through: 16

Branch
------
master

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

Modified Files
--------------
contrib/ltree/ltxtquery_io.c    |  8 ++++----
src/backend/utils/adt/tsquery.c | 14 +++++++++-----
2 files changed, 13 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Don't absorb child pathkeys into dummy AppendPaths for set-ops.
Next
From: Nathan Bossart
Date:
Subject: pgsql: Fix pg_blocking_pids() for relation extension locks.