aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-08-01 12:22:35 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-08-01 12:22:35 -0400
commit331f8b851c980d4050a82c1de101f93d47ddaacf (patch)
tree1571af9d2ab0cdc5ac4034c4ebcb72d06dac88f7 /src/backend/access/gist/gistget.c
parentaadaaeff4cf8b90c62dbb6cc67f5dd7e5a0297fe (diff)
downloadpostgresql-331f8b851c980d4050a82c1de101f93d47ddaacf.tar.gz
postgresql-331f8b851c980d4050a82c1de101f93d47ddaacf.zip
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
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions