Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Date: 2013-11-27 09:29:59
Message-ID: CAM3SWZQe-KiA79d4=6FBQK4Rgg0RVbWkYT6JnN2qJ+qCPWbzHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 27, 2013 at 1:20 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Even the "deadlock detected" errors might be a fkey-locking issue. Bug
> #8434, but that's really hard to know without more details.

Thanks, I was aware of that but didn't make the connection.

I've written a test-case that is designed to exercise one case that
deadlocks like crazy - deadlocking is the expected, correct behavior.
The deadlock errors are not in themselves suspicious. Actually, if
anything I find it suspicious that there aren't more deadlocks.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mohsen soodkhah mohammadi 2013-11-27 09:30:53 Name type in postgres
Previous Message Naoya Anzai 2013-11-27 09:24:12 Re: PostgreSQL Service on Windows does not start. ~ "is not a valid Win32 application"