Re: dynamic shared memory and locks
От | Tom Lane |
---|---|
Тема | Re: dynamic shared memory and locks |
Дата | |
Msg-id | 2790.1389020389@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: dynamic shared memory and locks (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: dynamic shared memory and locks
Re: dynamic shared memory and locks |
Список | pgsql-hackers |
Andres Freund <andres@2ndquadrant.com> writes: > On 2014-01-06 10:35:59 +0200, Heikki Linnakangas wrote: >> That assumes that you never hold more than one spinlock at a time, otherwise >> you can get deadlocks. I think that assumptions holds currently, because >> acquiring two spinlocks at a time would be bad on performance grounds >> anyway. > I think that's a pretty dangerous assumption I think it's a fine assumption. Code that could possibly do that should never get within hailing distance of being committed, because you are only supposed to have short straight-line bits of code under a spinlock. Taking another spinlock breaks both the "straight line code" and the "no loops" aspects of that coding rule. regards, tom lane
В списке pgsql-hackers по дате отправления: