| From: | Robert Haas <rhaas(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix possible infinite loop with Parallel Append. |
| Date: | 2018-02-08 17:57:31 |
| Message-ID: | E1ejqRv-0001uE-TD@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix possible infinite loop with Parallel Append.
When the previously-chosen plan was non-partial, all pa_finished
flags for partial plans are now set, and pa_next_plan has not yet
been set to INVALID_SUBPLAN_INDEX, the previous code could go into
an infinite loop.
Report by Rajkumar Raghuwanshi. Patch by Amit Khandekar and me.
Review by Kyotaro Horiguchi.
Discussion: http://postgr.es/m/CAJ3gD9cf43z78qY=U=H0HvOEN341qfRO-vLpnKPSviHeWgJQ5w@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/88fdc7006018b92d6ec92c54b3819764703daaba
Modified Files
--------------
src/backend/executor/nodeAppend.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-02-08 19:30:59 | pgsql: Avoid listing the same ResultRelInfo in more than one EState lis |
| Previous Message | Peter Eisentraut | 2018-02-08 14:59:42 | pgsql: Refine SSL tests test name reporting |