pgsql: Prevent stack overflow in container-type functions.

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Prevent stack overflow in container-type functions.
Date: 2015-10-05 14:09:49
Message-ID: [email protected]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/0398e071adf5437bafaab7701dc46df55dceca76

Modified Files
--------------
src/backend/utils/adt/rowtypes.c | 13 +++++++++++++
1 file changed, 13 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2015-10-05 14:15:00 pgsql: Add regression tests for INSERT/UPDATE+RETURNING
Previous Message Tom Lane 2015-10-05 13:51:31 Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values.