pgsql: Check maximum number of columns in function RTEs, too. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Check maximum number of columns in function RTEs, too.
Date
Msg-id E1oIYC1-002HGq-M4@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Check maximum number of columns in function RTEs, too.

I thought commit fd96d14d9 had plugged all the holes of this sort,
but no, function RTEs could produce oversize tuples too, either
via long coldeflists or just from multiple functions in one RTE.
(I'm pretty sure the other variants of base RTEs aren't a problem,
because they ultimately refer to either a table or a sub-SELECT,
whose widths are enforced elsewhere.  But we explicitly allow join
RTEs to be overwidth, as long as you don't try to form their
tuple result.)

Per further discussion of bug #17561.  As before, patch all branches.

Discussion: https://postgr.es/m/17561-80350151b9ad2ad4@postgresql.org

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/51d8b52fcf8c9fcffca9c6a54e5df9d66d51c82f

Modified Files
--------------
src/backend/parser/parse_relation.c | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone
Next
From: David Rowley
Date:
Subject: pgsql: Have ExecFindPartition cache the last found partition