Re: Overhead cost of Serializable Snapshot Isolation
| От | Simon Riggs |
|---|---|
| Тема | Re: Overhead cost of Serializable Snapshot Isolation |
| Дата | |
| Msg-id | CA+U5nMLo+KL_X3Q9_QCQ3e=i12ioPAQgp3tqfKFDrgKw5gOReA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Overhead cost of Serializable Snapshot Isolation ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: Overhead cost of Serializable Snapshot Isolation
|
| Список | pgsql-hackers |
On Mon, Oct 10, 2011 at 11:31 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > Simon Riggs <simon@2ndQuadrant.com> wrote: > >> How do we turn it on/off to allow the overhead to be measured? > > User REPEATABLE READ transactions or SERIALIZABLE transactions. The > easiest way, if you're doing it for all transactions (which I > recommend) is to set default_transaction_isolation. Most apps use mixed mode serializable/repeatable read and therefore can't be changed by simple parameter. Rewriting the application isn't a sensible solution. I think it's clear that SSI should have had and still needs an "off switch" for cases that cause performance problems. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: