Re: Adding MERGE to the TODO list (resend with subject)
От | Christopher Kings-Lynne |
---|---|
Тема | Re: Adding MERGE to the TODO list (resend with subject) |
Дата | |
Msg-id | 409DC28A.7010509@familyhealth.com.au обсуждение исходный текст |
Ответ на | Re: Adding MERGE to the TODO list (resend with subject) (Alvaro Herrera <alvherre@dcc.uchile.cl>) |
Ответы |
Re: Adding MERGE to the TODO list (resend with subject)
Re: Adding MERGE to the TODO list (resend with subject) |
Список | pgsql-hackers |
>>Except you can keep trying and trying without the outermost transaction >>failing. > > But that won't provide the necessary next key locking you mentioned in > your first email, will it? No, but since I can loop an infinite number of times until either the update or insert works, I don't need next key locking. BTW, the reference in MySQL: http://dev.mysql.com/doc/mysql/en/REPLACE.html Hmm...no refernce to next key locking. Maybe that's an Innodb thing... Anyway, you can see how they've implemented their algorithm. Here is docs on the DB2 merge command from which the standard was derived: http://databasejournal.com/features/db2/article.php/10896_3322041_2 Chris
В списке pgsql-hackers по дате отправления: