Re: pgsql: Set partitioned_rels appropriately when UNION ALL is used.

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Robert Haas <rhaas(at)postgresql(dot)org>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Set partitioned_rels appropriately when UNION ALL is used.
Date: 2017-09-19 23:59:50
Message-ID: CAEepm=2j-HAgnBUrAazwS0ry7Z_ihk+d7g+Ye3u99+6WbiGt_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Fri, Sep 15, 2017 at 3:06 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> 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
> ------
> master
>
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/1555566d9ee1a996a28cc4601840a67831112695
>
> Modified Files
> --------------
> src/backend/optimizer/path/allpaths.c | 42 +++++++++++++++++++++++++++++++----
> src/backend/optimizer/plan/planner.c | 6 ++---
> 2 files changed, 40 insertions(+), 8 deletions(-)

I spotted a typo: s/unexpcted/unexpected/.

--
Thomas Munro
http://www.enterprisedb.com

Attachment Content-Type Size
typo.patch application/octet-stream 491 bytes

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-09-20 01:06:29 Re: pgsql: Make new crash restart test a bit more robust.
Previous Message Andres Freund 2017-09-19 23:46:13 pgsql: s/NULL byte/NUL byte/ in comment refering to C string terminator