From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Andres Freund <andres(at)2ndQuadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Improve concurrency of foreign key locking |
Date: | 2013-01-23 23:14:39 |
Message-ID: | 28962.1358982879@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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.
> Hint: there are no rows to lock
This bit doesn't seem to be either accurate or helpful, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-01-24 03:09:00 | pgsql: Fix failure to rotate postmaster log file for size reasons on Wi |
Previous Message | Andrew Dunstan | 2013-01-23 21:23:49 | Re: [COMMITTERS] pgsql: Improve concurrency of foreign key locking |
From | Date | Subject | |
---|---|---|---|
Next Message | Phil Sorber | 2013-01-23 23:47:54 | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |
Previous Message | Tom Lane | 2013-01-23 23:07:51 | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |