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

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Peter Geoghegan <pg(at)heroku(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 11:57:29
Message-ID: 52F8BEA9.8030204@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/07/2014 01:27 PM, Peter Geoghegan wrote:
> On Thu, Jan 16, 2014 at 12:35 AM, Heikki Linnakangas
> <hlinnakangas(at)vmware(dot)com> wrote:
>>> I think you should consider breaking off the relcache parts of my
>>> patch and committing them, because they're independently useful.
>>
>> Makes sense. Can you extract that into a separate patch, please?
>
> Perhaps you can take a look at this again, when you get a chance.

The relcache parts? I don't think a separate patch ever appeared that
could be reviewed.

Looking again at the last emails in this whole thread, I don't have
anything to add. At this point, I think it's pretty clear this won't
make it into 9.4, so I'm going to mark this as "returned with feedback".
If someone else thinks this still has a chance and is willing to review
this and beat it into shape, please resurrect it quickly.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2014-02-10 12:00:47 Re: inherit support for foreign tables
Previous Message Christian Convey 2014-02-10 11:45:18 Re: Breaking compile-time dependency cycles of Postgres subdirs?