pgsql: Prevent stack overflow in container-type functions. - Mailing list pgsql-committers

From Noah Misch
Subject pgsql: Prevent stack overflow in container-type functions.
Date
Msg-id E1Zj6Sb-0005da-7N@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Prevent stack overflow in container-type functions.

A range type can name another range type as its subtype, and a record
type can bear a column of another record type.  Consequently, functions
like range_cmp() and record_recv() are recursive.  Functions at risk
include operator family members and referents of pg_type regproc
columns.  Treat as recursive any such function that looks up and calls
the same-purpose function for a record column type or the range subtype.
Back-patch to 9.0 (all supported versions).

An array type's element type is never itself an array type, so array
functions are unaffected.  Recursion depth proportional to array
dimensionality, found in array_dim_to_jsonb(), is fine thanks to MAXDIM.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/9286ff78f8a5dbb7edec678c4873c63b56266193

Modified Files
--------------
src/backend/utils/adt/rangetypes.c |   13 +++++++++++++
src/backend/utils/adt/rowtypes.c   |   13 +++++++++++++
2 files changed, 26 insertions(+)


pgsql-committers by date:

Previous
From: Noah Misch
Date:
Subject: pgsql: Prevent stack overflow in container-type functions.
Next
From: Noah Misch
Date:
Subject: pgsql: Prevent stack overflow in query-type functions.