Re: someone working to add merge? - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: someone working to add merge?
Date
Msg-id c2d9e70e0511110915o2a165a4pf6e83ef852b6e06@mail.gmail.com
Whole thread Raw
In response to Re: someone working to add merge?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: someone working to add merge?
Re: someone working to add merge?
List pgsql-hackers
On 11/11/05, Josh Berkus <josh@agliodbs.com> wrote:
> Jaime,
>
> > so i suppose we can reuse many of the code breaking the merge in 3
> > pieces... for now they are just thougths, i will think more in this
> > and try to implement it...
> >
> > comments? ideas? suggestions?
>
> Funny, we were just discussing this at OpenDBCon.   Seems that you can't do a
> full implementation of MERGE without Predicate Locking (the ability to say
> "lock this table against inserts or updates of any row with key=5").

it isn't what select for update does?

> However, Peter suggested that we could do a proof-of-concept implementation,
> working out syntax and trigger issues, based on a full table lock and do the
> hard work once it was proved to be feasable.
>
> Peter?
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>

--
Atentamente,
Jaime Casanova
(DBA: DataBase Aniquilator ;)


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: someone working to add merge?
Next
From: Andrew Dunstan
Date:
Subject: Re: someone working to add merge?