Horton

Re: Re: new patch of MERGE (merge_204) & a question about duplicated ctid

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Greg Smith <greg@2ndquadrant.com>, Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>, Boxuan Zhai <bxzhai2010@gmail.com>, pgsql-hackers@postgresql.org
Date: 2011-01-03T16:06:15Z
Lists: pgsql-hackers 

On 01/03/2011 10:58 AM, Heikki Linnakangas wrote:
>>
>> In general, I also thought/expected to have some kind of UPSERT type
>> capability with our initial MERGE support, even if it requires a big
>> lock and won't operate concurrently, etc.
>
>
> You can of course LOCK TABLE as a work-around, if that's what you want.

I think we need to state this in large red letters in the docs, if 
that's the requirement.

cheers

andrew