Re: parallel "return query" is no good - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel "return query" is no good
Date
Msg-id CA+TgmoZZMG9hRbC0ANBdakHyZ8-2Hpa=kKyrOFGM8c78wQx-fg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] parallel "return query" is no good  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Thu, Mar 23, 2017 at 1:53 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Robert Haas wrote:
>> I guess the downside of back-patching this is that it could cause a
>> plan change for somebody which ends up being worse.  On the whole,
>> serial execution of queries intended to be run in parallel isn't
>> likely to work out well, but it's always possible somebody has a cases
>> where it happens to be winning, and this could break it.  So maybe I
>> should do this only in master?  Thoughts?
>
> I think that the chances of someone depending on a parallel plan running
> serially by accident which is better than the non-parallel plan, are
> pretty slim.
>
> +1 for back-patching.

All right, done.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Next
From: Dave Page
Date:
Subject: Re: Monitoring roles patch