Re: gSoC add MERGE command new patch -- merge_v104 - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: gSoC add MERGE command new patch -- merge_v104
Date
Msg-id 4C7644D3.4090400@cs.helsinki.fi
Whole thread Raw
In response to Re: gSoC add MERGE command new patch -- merge_v104  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On 2010-08-25 12:44 PM +0300, Heikki Linnakangas wrote:
> On 25/08/10 12:41, Andres Freund wrote:
>> But randomly loosing tuples will make much more people unhappy. At a
>> much more problematic point of time (in production).
>
> Hmm, how would you lose tuples?

I think what Andres means is: T1 starts a MERGE.  INSERT fails because 
the tuple already exists, but then another transaction, T2, DELETEs that 
tuple.  T1 tries to UPDATE it, but fails because it doesn't exist 
anymore.  Not T1 should go back and INSERT the tuple, but that isn't 
what happens with this patch, is it?


Regards,
Marko Tiikkaja


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!)
Next
From: Markus Wanner
Date:
Subject: Re: bg worker: patch 1 of 6 - permanent process