Re: MERGE Specification - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: MERGE Specification
Date
Msg-id 20080422202057.GG9883@svana.org
Whole thread Raw
In response to Re: MERGE Specification  (Decibel! <decibel@decibel.org>)
Responses Re: MERGE Specification  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
On Tue, Apr 22, 2008 at 02:19:24PM -0500, Decibel! wrote:
> But no matter how this is done, I think we need to handle the race
> conditions, and handle them by default. If people *really* know what
> they're doing, they can disable the row locking (perhaps one way to
> do this would be to grab an explicit lock on the table and have merge
> check for that...).

I disagree. The spec doesn't require it and MERGE is useful without it.
For a first cut I would say implement as the spec says, race conditions
and all. Later we can think on whether it's worth handling them
directly.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

pgsql-hackers by date:

Previous
From: "Gurjeet Singh"
Date:
Subject: RECORD.* doesn't work in Pl/PGSQL
Next
From: James Mansion
Date:
Subject: Re: pgkill on win32