From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, James Sewell <james(dot)sewell(at)lisasoft(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andreas Ulbrich <andreas(dot)ulbrich(at)matheversum(dot)de> |
Subject: | Re: Choosing parallel_degree |
Date: | 2016-04-12 06:58:23 |
Message-ID: | CAA4eK1K__p+=Am-Lw55wAj5d=QaiSagtZqwHZ2+K+y_MwwN_qw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 12, 2016 at 3:15 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 8 April 2016 at 17:49, Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-04-12 07:03:41 | Update copyright in genericdesc.c |
Previous Message | Noah Misch | 2016-04-12 06:43:22 | Re: GIN data corruption bug(s) in 9.6devel |