From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)endpoint(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Overhead cost of Serializable Snapshot Isolation |
Date: | 2011-10-11 20:29:19 |
Message-ID: | CA+U5nML3UOTukxSEaFkr03wgL1FJJb23UuhdJQX_tZhr6x5LUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 11, 2011 at 9:21 PM, Greg Sabino Mullane <greg(at)endpoint(dot)com> wrote:
> Simon Riggs:
>> 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.
>
> Eh? It has an off switch: repeatable read.
You mean: if we recode the application and retest it, we can get it to
work same way as it used to.
To most people that is the same thing as "it doesn't work with this
release", ask any application vendor.
There is no off switch and there should be.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-10-11 20:32:45 | Re: Overhead cost of Serializable Snapshot Isolation |
Previous Message | Andrew Dunstan | 2011-10-11 20:29:18 | Re: Dumping roles improvements? |