Re: MERGE Specification
Martijn van Oosterhout <kleptog@svana.org>
From: Martijn van Oosterhout <kleptog@svana.org>
To: Decibel! <decibel@decibel.org>
Cc: Gregory Stark <stark@enterprisedb.com>, Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, "A.M." <agentm@themactionfaction.com>, pgsql-hackers@postgresql.org
Date: 2008-04-22T20:20:57Z
Lists: 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.