Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
От | Peter Geoghegan |
---|---|
Тема | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
Дата | |
Msg-id | CAM3SWZS7cwYa6_Qfv3M2N1t5eekMkHbBNdRUswZ1bT9MJ11CDg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
|
Список | pgsql-hackers |
On Fri, Jan 10, 2014 at 7:12 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > I'm getting deadlocks with this patch, using the test script you posted > earlier in > http://www.postgresql.org/message-id/CAM3SWZQh=8xNVgbBzYHJeXUJBHwZNjUTjEZ9t-DBO9t_mX_8Kw@mail.gmail.com. > Am doing something wrong, or is that a regression? Yes. The point of that test case was that it made your V1 livelock (which you fixed), not deadlock in a way detected by the deadlock detector, which is the correct behavior. This testcase was the one that showed up *unprincipled* deadlocking: http://www.postgresql.org/message-id/CAM3SWZShbE29KpoD44cVc3vpZJGmDer6k_6FGHiSzeOZGmTFSQ@mail.gmail.com I'd focus on that test case. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: