From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl |
Date: | 2016-02-17 04:12:46 |
Message-ID: | CA+Tgmob5aM=txM13KgdGcVU+aY1O+r24fPGOaj4wWLZBetLbog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Feb 16, 2016 at 8:37 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 14 February 2016 at 08:05, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> The concept of a
>> lock group is formally separate from the concept of a parallel group
>> created by a ParallelContext, but it is not clear that there will ever
>> be any other context in which a lock group will be a good idea.
>
> Just coming back to this in terms of what Stephen and I raised: Robert, do
> you think this design as it stands can handle cases where a normal
> standalone backend gets promoted to a lock-group leader that others can then
> join?
That's the exact intended purpose of it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-02-17 04:22:40 | Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl |
Previous Message | Tom Lane | 2016-02-17 02:08:37 | pgsql: Make plpython cope with funny characters in function names. |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-02-17 04:12:48 | Re: Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates) |
Previous Message | Pavel Stehule | 2016-02-17 04:07:41 | Re: proposal: enhancing slow query log, and autoexplain log about waiting on lock before query exec time |