diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-03 16:16:36 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-03 16:16:36 -0500 |
| commit | 92f87182f2c617fd420832972b6d0ae4527301c8 (patch) | |
| tree | b79a003f6dd640d8c6fc6dfa6a69956ea59616ef /src/backend/executor/nodeIncrementalSort.c | |
| parent | 17fb60387ce3fdc2bbb13d9b67bed0e4da77e173 (diff) | |
| download | postgresql-92f87182f2c617fd420832972b6d0ae4527301c8.tar.gz postgresql-92f87182f2c617fd420832972b6d0ae4527301c8.zip | |
Guard against core dump from uninitialized subplan.
If the planner erroneously puts a non-parallel-safe SubPlan into
a parallelized portion of the query tree, nodeSubplan.c will fail
in the worker processes because it finds a null in es_subplanstates,
which it's unable to cope with. It seems worth a test-and-elog to
make that an error case rather than a core dump case.
This probably should have been included in commit 16ebab688, which
was responsible for allowing nulls to appear in es_subplanstates
to begin with. So, back-patch to v10 where that came in.
Discussion: https://postgr.es/m/924226.1604422326@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeIncrementalSort.c')
0 files changed, 0 insertions, 0 deletions