Re: Gather Merge

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Gather Merge
Date: 2017-03-10 09:12:48
Message-ID: VisenaEmail.2a.7febb91868fbbb2.15ab77c9e61@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

På fredag 10. mars 2017 kl. 10:09:22, skrev Rushabh Lathia <
rushabh(dot)lathia(at)gmail(dot)com <mailto:rushabh(dot)lathia(at)gmail(dot)com>>:
    On Fri, Mar 10, 2017 at 2:33 PM, Andreas Joseph Krogh <andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com>> wrote: [...]

The execution-plan seems (unsurprisingly) to depend on data-distribution, so
is there a way I can force a GatherMerge?
 
Not directly. GatherMerge cost is mainly depend on parallel_setup_cost,
parallel_tuple_cost and cpu_operator_cost. May be you can force this
by setting this cost low enough. Or another way to force is by disable the
other plans.
 
What plan you are getting now? You not seeing the below error ?
 
ERROR:  GatherMerge child's targetlist doesn't match GatherMerge

 
I'm seeing the same error, it's just that for reproducing it I'd rather not
copy my whole dataset.
 
-- Andreas Joseph Krogh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Surafel Temesgen 2017-03-10 09:13:11 Re: New CORRESPONDING clause design
Previous Message Rushabh Lathia 2017-03-10 09:09:22 Re: Gather Merge