Re: Unexpected planner choice in simple JOIN - Mailing list pgsql-performance

From Tom Lane
Subject Re: Unexpected planner choice in simple JOIN
Date
Msg-id 1895375.1767846864@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected planner choice in simple JOIN  (Mark Kirkwood <mark.kirkwood@gmail.com>)
Responses Re: Unexpected planner choice in simple JOIN
List pgsql-performance
Mark Kirkwood <mark.kirkwood@gmail.com> writes:
> Good suggestion. The results are...interesting:

It's clear that the planner is underestimating the costs of using a
parallel worker in your setup.  Try increasing parallel_setup_cost
and/or parallel_tuple_cost to bring things more in line with reality.

            regards, tom lane



pgsql-performance by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Unexpected planner choice in simple JOIN
Next
From: Mark Kirkwood
Date:
Subject: Re: Unexpected planner choice in simple JOIN