Horton

Re: regression, deadlock in high frequency single-row UPDATE

Mark Kirkwood <mark.kirkwood@catalyst.net.nz>

View thread View on postgr.es
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Andrew Sackville-West <awest@janrain.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-bugs@postgresql.org, Paulo Tanimoto <paulo@janrain.com>
Date: 2014-12-10T03:07:30Z
Lists: pgsql-bugs 
On 10/12/14 06:28, Andrew Sackville-West wrote:
> On Mon, Dec 8, 2014 at 9:58 PM, Mark Kirkwood

>     Just mucking about I changed certain things in your schema setup
>     (removed ON DELETE CASCADE, use CURRENT_TIMESTAMP instead of
>     now()...lessen the use of DEFAULT)...however still seeing deadlocks
>     in 9.4, so at least it is easy to reproduce!
>
>
> Can you speak to what benefits those changes might yield? Or point to
> relevant docs?
>

Not so much advantages - just seeing if I could still reproduce the 
issue with a simpler test case i.e ensuring you were not doing anything 
'odd' - and you are not :-)

The next step would be trying to figure out what commit introduced this 
behaviour - but depesz has already beaten me to that (nice work)!

Cheers

Mark

Commits

  1. Add isolationtester spec for old heapam.c bug

  2. Improve concurrency of foreign key locking