Re: [PATCH] SQL assertions prototype

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: [PATCH] SQL assertions prototype
Дата
Msg-id
52C9BC46.1010505@gmx.net
Ответ на
Re: [PATCH] SQL assertions prototype (Andres Freund)
Список
Дерево обсуждения
[PATCH] SQL assertions prototype Peter Eisentraut <peter_e@gmx.net>
Re: [PATCH] SQL assertions prototype Heikki Linnakangas <hlinnakangas@vmware.com>
Re: [PATCH] SQL assertions prototype Simon Riggs <simon@2ndQuadrant.com>
Re: [PATCH] SQL assertions prototype Peter Eisentraut <peter_e@gmx.net>
Re: [PATCH] SQL assertions prototype Andrew Tipton <andrew@kiwidrew.com>
Re: [PATCH] SQL assertions prototype Kevin Grittner <kgrittn@ymail.com>
Re: [PATCH] SQL assertions prototype David Fetter <david@fetter.org>
Re: [PATCH] SQL assertions prototype Kevin Grittner <kgrittn@ymail.com>
Re: [PATCH] SQL assertions prototype David Fetter <david@fetter.org>
Re: [PATCH] SQL assertions prototype Pavel Stehule <pavel.stehule@gmail.com> 
On 12/18/13, 2:22 PM, Andres Freund wrote:
> It would only force serialization for transactions that modify tables
> covered by the assert, that doesn't seem to bad. Anything covered by an
> assert shoulnd't be modified frequently, otherwise you'll run into major
> performance problems.

I think that makes sense.  If you want to use assertions, you need to
run in serializable mode, otherwise you get an error if you modify
anything covered by an assertion.

In the future, someone could enhance this for other isolation levels,
but as Josh has pointed out, that would likely just be reimplementing
SSI with big locks.
В списке pgsql-hackers по дате отправления
Предыдущее
От: Mark Dilger
Дата:
Следующее
От: Peter Eisentraut
Дата:
FAQ