Re: Implementing SQL ASSERTION
От | Fabien COELHO |
---|---|
Тема | Re: Implementing SQL ASSERTION |
Дата | |
Msg-id | alpine.DEB.2.20.1801151357080.11126@lancre обсуждение исходный текст |
Ответ на | Re: Implementing SQL ASSERTION (Joe Wildish <joe-postgresql.org@elusive.cx>) |
Ответы |
Re: Implementing SQL ASSERTION
|
Список | pgsql-hackers |
>> I'm wondering about the effect of MVVC on this: if the check is >> performed when the INSERT is done, concurrent inserting transactions >> would count the current status which would be ok, but on commit all >> concurrent inserts would be there and the count could not be ok >> anymore? > The patch doesn’t attempt to address concurrency (beyond the obvious > benefit of reducing the circumstances under which the assertion is > checked). I am working under the assumption that we will find some > acceptable way for that to be resolved :-) And at the moment, working in > serialisable mode addresses this issue. I think that is suggested in the > thread actually (essentially, if you want to use assertions, you require > that transactions be performed at serialisable isolation level). Thanks for the pointers. The "serializable" isolation level restriction sounds reasonnable. -- Fabien.
В списке pgsql-hackers по дате отправления: