Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "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 14:25:48
Message-ID: 14623.1455719148@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I guess it's worth pointing out that storing the groupLeader in the
> PROCLOCK, as we do currently, avoids this issue entirely.

Right, that's why I framed it as "can we salvage this simplification"
(referring to removal of that field). It may be best to just fix the
existing bug and docs deficiencies before returning to that idea.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-02-17 14:52:12 Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Previous Message Robert Haas 2016-02-17 10:12:46 pgsql: Reuse abbreviated keys in ordered [set] aggregates.

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-02-17 14:32:22 Re: proposal: PL/Pythonu - function ereport
Previous Message Artur Zakirov 2016-02-17 13:22:27 Re: [PROPOSAL] Improvements of Hunspell dictionaries support