From: | Robert Haas <rhaas(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Set partitioned_rels appropriately when UNION ALL is used. |
Date: | 2017-09-14 15:06:51 |
Message-ID: | E1dsVj9-00083s-2v@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Set partitioned_rels appropriately when UNION ALL is used.
In most cases, this omission won't matter, because the appropriate
locks will have been acquired during parse/plan or by AcquireExecutorLocks.
But it's a bug all the same.
Report by Ashutosh Bapat. Patch by me, reviewed by Amit Langote.
Discussion: http://postgr.es/m/CAFjFpRdHb_ZnoDTuBXqrudWXh3H1ibLkr6nHsCFT96fSK4DXtA@mail.gmail.com
Branch
------
REL_10_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/448aa36e8b969da257bb58a6fe3db6498d48d4e8
Modified Files
--------------
src/backend/optimizer/path/allpaths.c | 42 +++++++++++++++++++++++++++++++----
src/backend/optimizer/plan/planner.c | 6 ++---
2 files changed, 40 insertions(+), 8 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-09-14 15:10:14 | Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
Previous Message | Andres Freund | 2017-09-14 09:06:20 | pgsql: Properly check interrupts in execScan.c. |