Re: [COMMITTERS] pgsql: Improve concurrency of foreign key locking

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Andres Freund <andres(at)2ndQuadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Improve concurrency of foreign key locking
Date: 2013-02-06 03:30:26
Message-ID: 20130206033026.GJ5753@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > On 23 January 2013 17:15, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> >> On 2013-01-23 11:58:28 -0500, Andrew Dunstan wrote:
> >>> Can't we do better than that?
>
> > "row level locks cannot be applied to the NULLable side of an outer join"
>
> I think it should read "row-level locks cannot ...", but otherwise this
> is a fine idea.

Thanks for the suggestion, I have changed all these messages.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-06 11:48:34 pgsql: Split out list of XLog resource managers
Previous Message Alvaro Herrera 2013-02-06 03:21:25 pgsql: Improve error message wording

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-06 03:42:31 Re: sql_drop Event Trigger
Previous Message Alvaro Herrera 2013-02-05 23:58:02 Re: sql_drop Event Trigger