Re: Oddity with parallel safety test for scan/join target in grouping_planner

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oddity with parallel safety test for scan/join target in grouping_planner
Date: 2019-02-27 15:52:32
Message-ID: CA+TgmobmV=Zw2OEJKUorJe=e+_fCzsvYErR6tXxTjCzK45x9RQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 26, 2019 at 7:26 AM Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> The parallel safety of the final scan/join target is determined from the
> grouping target, not that target, which [ is wrong ]

OOPS. That's pretty embarrassing.

Your patch looks right to me. I will now go look for a bag to put over my head.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-02-27 15:55:49 Re: reloption to prevent VACUUM from truncating empty pages at the end of relation
Previous Message Robert Haas 2019-02-27 15:46:23 Re: Unneeded parallel safety tests in grouping_planner