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-07 11:27:38
Message-ID: CAM3SWZQ1PaGGyS4AUMeErT0c=QR=xtLQt22KZrb0tNJ9gEQPZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2014-02-07 12:31:02 Re: inherit support for foreign tables
Previous Message Andres Freund 2014-02-07 10:18:33 Re: Recovery inconsistencies, standby much larger than primary