Re: Choosing parallel_degree

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Choosing parallel_degree
Date: 2016-09-01 13:39:39
Message-ID: CANP8+jKso6g5XhwrBCCUWMQz-5RiO1CjWWbjF=COfGRAhde4Hw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 April 2016 at 14:11, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 12 April 2016 at 13:53, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>> On Mon, Apr 11, 2016 at 5:45 PM, 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.
>> >
>> > Can I change this to a lower setting? I would have done this before
>> > applying
>> > the patch, but you beat me to it.
>>
>> I don't have a problem with reducing the lock level there, if we're
>> convinced that it's safe.
>
>
> I'll run up a patch, with appropriate comments.

Attached

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
reduce_lock_levels_incl_comments.patch application/octet-stream 5.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Constantin S. Pan 2016-09-01 13:42:03 Re: autonomous transactions
Previous Message Michael Paquier 2016-09-01 13:30:10 Re: Missing checks when malloc returns NULL...