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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Date: 2014-02-10 18:05:31
Message-ID: CAM3SWZQE0vZJw1HNKnUwqE58RjvcWOsY8JVbu8YjqHrSLK806w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 10, 2014 at 11:57 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> The relcache parts? I don't think a separate patch ever appeared that could
> be reviewed.

I posted the patch on January 18th:
http://www.postgresql.org/message-id/CAM3SWZTh4VkESoT7dCrWbPRN7zZhNZ-Wa6zmvO1FF7gBNOjNOg@mail.gmail.com

I was under the impression that you agreed that this was independently
valuable, regardless of the outcome here.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-02-10 18:13:11 Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Previous Message Tom Lane 2014-02-10 18:03:38 Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease