diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-19 13:54:45 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-19 13:54:45 -0400 |
| commit | 04dae19f4d5067b35b421dcd43175a5059747800 (patch) | |
| tree | d327028fa52d0dfb470a78ee90732c4007feecd7 /src/backend/commands/tablecmds.c | |
| parent | f627fd547a34bb3ffba5763a1ab404c2777debe4 (diff) | |
| download | postgresql-04dae19f4d5067b35b421dcd43175a5059747800.tar.gz postgresql-04dae19f4d5067b35b421dcd43175a5059747800.zip | |
Fix assignment to array of domain over composite.
An update such as "UPDATE ... SET fld[n].subfld = whatever"
failed if the array elements were domains rather than plain
composites. That's because isAssignmentIndirectionExpr()
failed to cope with the CoerceToDomain node that would appear
in the expression tree in this case. The result would typically
be a crash, and even if we accidentally didn't crash, we'd not
correctly preserve other fields of the same array element.
Per report from Onder Kalaci. Back-patch to v11 where arrays of
domains came in.
Discussion: https://postgr.es/m/PH0PR21MB132823A46AA36F0685B7A29AD8BD9@PH0PR21MB1328.namprd21.prod.outlook.com
Diffstat (limited to 'src/backend/commands/tablecmds.c')
0 files changed, 0 insertions, 0 deletions