From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: someone working to add merge? |
Date: | 2005-11-11 17:15:58 |
Message-ID: | c2d9e70e0511110915o2a165a4pf6e83ef852b6e06@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/11/05, Josh Berkus <josh(at)agliodbs(dot)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 ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-11-11 17:26:54 | Re: someone working to add merge? |
Previous Message | Josh Berkus | 2005-11-11 17:09:45 | Re: someone working to add merge? |