Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl
Date
Msg-id CAMsr+YFqJCNBjO-T9vsyRQshDN4kRHhhkia_jcYxnRKzL6zocA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl
List pgsql-hackers
On 14 February 2016 at 08:05, Robert Haas <robertmhaas@gmail.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? 

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: pglogical - logical replication contrib module
Next
From: Jim Nasby
Date:
Subject: Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates)