diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-01 12:22:35 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-01 12:22:35 -0400 |
| commit | 83f1793d6096deb419e16cc38201484a6f6e9f48 (patch) | |
| tree | 8a5c6bfcd75300d651fc4e8f516f2c79da68d202 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 8b1ec7d2953273501c5cea8185b6358dc7709eb5 (diff) | |
| download | postgresql-83f1793d6096deb419e16cc38201484a6f6e9f48.tar.gz postgresql-83f1793d6096deb419e16cc38201484a6f6e9f48.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/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions