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: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Date: 2013-12-12 09:47:14
Message-ID: CAM3SWZQj0W2pt+xFQQp2VSTksN0+twSFbGYhDp4B81YHVGqf3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 12, 2013 at 1:23 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> What's the status of this patch? I posted my version using a quite different
> approach than your original patch. You did some testing of that, and ran
> into unrelated bugs. Have they been fixed now?

Sorry, I dropped the ball on this. I'm doing a bit more testing of an
approach to fixing the new bugs. I'll let you know how I get on
tomorrow (later today for you).

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message knizhnik 2013-12-12 10:02:24 Re: In-Memory Columnar Store
Previous Message Heikki Linnakangas 2013-12-12 09:23:17 Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE