diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-19 11:35:15 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-19 11:35:15 -0400 |
| commit | 697dd1925f418c9f54ee1fd1cefbc613d6504b1f (patch) | |
| tree | 2c580255297845fe66ea77e1895bf64d5fd11ab8 /src/backend/executor | |
| parent | 998d060f3db79c6918cb4a547695be150833f9a4 (diff) | |
| download | postgresql-697dd1925f418c9f54ee1fd1cefbc613d6504b1f.tar.gz postgresql-697dd1925f418c9f54ee1fd1cefbc613d6504b1f.zip | |
Remove bogus assertion in transformExpressionList().
I think when I added this assertion (in commit 8f889b108), I was only
thinking of the use of transformExpressionList at top level of INSERT
and VALUES. But it's also called by transformRowExpr(), which can
certainly occur in an UPDATE targetlist, so it's inappropriate to
suppose that p_multiassign_exprs must be empty. Besides, since the
input is not expected to contain ResTargets, there's no reason it
should contain MultiAssignRefs either. Hence this code need not
be concerned about the state of p_multiassign_exprs, and we should
just drop the assertion.
Per bug #17236 from ocean_li_996. It's been wrong for years,
so back-patch to all supported branches.
Discussion: https://postgr.es/m/17236-3210de9bcba1d7ca@postgresql.org
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions