diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2021-02-15 09:28:08 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2021-02-15 09:29:39 +0200 |
| commit | 18cacf89b9fe5523941b57fbd01d408585e70737 (patch) | |
| tree | 88af82b3ec4734e2d6c1365c48de8c02d7dc93c9 /src/backend/executor/nodeProjectSet.c | |
| parent | 6c23e5ae9ee12ff1f5183573885bfaa4eb97b243 (diff) | |
| download | postgresql-18cacf89b9fe5523941b57fbd01d408585e70737.tar.gz postgresql-18cacf89b9fe5523941b57fbd01d408585e70737.zip | |
Make ExecGetInsertedCols() and friends more robust and improve comments.
If ExecGetInsertedCols(), ExecGetUpdatedCols() or ExecGetExtraUpdatedCols()
were called with a ResultRelInfo that's not in the range table and isn't a
partition routing target, the functions would dereference a NULL pointer,
relinfo->ri_RootResultRelInfo. Such ResultRelInfos are created when firing
RI triggers in tables that are not modified directly. None of the current
callers of these functions pass such relations, so this isn't a live bug,
but let's make them more robust.
Also update comment in ResultRelInfo; after commit 6214e2b228,
ri_RangeTableIndex is zero for ResultRelInfos created for partition tuple
routing.
Noted by Coverity. Backpatch down to v11, like commit 6214e2b228.
Reviewed-by: Tom Lane, Amit Langote
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions