Re: parallel joins, and better parallel explain - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel joins, and better parallel explain
Date
Msg-id CA+Tgmoaz8EYCY=vxfrpc1jPdSzMYrk7M2q5dBjy1sD2KwZs+hg@mail.gmail.com
Whole thread Raw
In response to Re: parallel joins, and better parallel explain  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: parallel joins, and better parallel explain  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Mon, Dec 14, 2015 at 8:38 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> set enable_hashjoin=off;
> set enable_mergejoin=off;

[ ... ]


> Now here the point to observe is that non-parallel case uses both less
> Execution time and Planning time to complete the statement.  There
> is a considerable increase in planning time without any benefit in
> execution.

So, you forced the query planner to give you a bad plan, and then
you're complaining that the plan is bad?  That's not a very surprising
result.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Fixing warnings in back branches?
Next
From: Tom Lane
Date:
Subject: Re: Fixing warnings in back branches?