Postgres Pro
Downloads
Home   >   mailing lists

Re: Choosing parallel_degree - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Choosing parallel_degree
Date
Msg-id CAA4eK1K__p+=Am-Lw55wAj5d=QaiSagtZqwHZ2+K+y_MwwN_qw@mail.gmail.com
Whole thread Raw
In response to Re: Choosing parallel_degree  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Choosing parallel_degree  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view
On Tue, Apr 12, 2016 at 3:15 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 8 April 2016 at 17:49, Robert Haas <robertmhaas@gmail.com> wrote:
 
With the patch, you can - if you wish - substitute
some other number for the one the planner comes up with.

I saw you're using AccessExclusiveLock, the reason being it affects SELECTs.

That is supposed to apply when things might change the answer from a SELECT, whereas this affects only the default for a plan.


By this theory, shouldn't any other parameter like n_distinct_inherited which just effects the plan required lower lock level?


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: GIN data corruption bug(s) in 9.6devel
Next
From: Amit Langote
Date:
Subject: Update copyright in genericdesc.c