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 | 205f958406cc85f8f73e151906ecd281ff05d80a (patch) | |
| tree | 3033bc585412494993912046d3a7d7389c16284d /src/backend/executor/nodeTableFuncscan.c | |
| parent | 501035a0ac7f711ee2f899cb08acb2a4237d7f4d (diff) | |
| download | postgresql-205f958406cc85f8f73e151906ecd281ff05d80a.tar.gz postgresql-205f958406cc85f8f73e151906ecd281ff05d80a.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/nodeTableFuncscan.c')
0 files changed, 0 insertions, 0 deletions