Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Date
Msg-id CAM3SWZTie8hMzTso3seacuiTw4TcOxygMtJQCKnQ3D0fOw0yww@mail.gmail.com
Whole thread Raw
In response to Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Mon, Dec 30, 2013 at 12:45 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2013-12-30 12:29:22 -0800, Peter Geoghegan wrote:
>> But even if that wasn't
>> true, I don't know why you feel the need to go on and on about buffer
>> locking like this months later. Are you trying to be provocative? Can
>> you *please* stop?
>
> ERR? Peter? *You* quoted a statement of mine that only made sense in
> it's original context. And I *did* say that the point about buffer
> locking applied to the *past* version of the patch.

Not so. You suggested it was a bug that needed to be fixed, completely
independently of this effort. You clearly referred to the current
code.

"Yes, it it is different. But, in my opinion, bt_check_unique() doing
so is a bug that needs fixing. Not something that we want to extend."

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Next
From: Adrian Klaver
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE