Re: Overhead cost of Serializable Snapshot Isolation - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Overhead cost of Serializable Snapshot Isolation
Date
Msg-id CA+U5nML3UOTukxSEaFkr03wgL1FJJb23UuhdJQX_tZhr6x5LUw@mail.gmail.com
Whole thread Raw
In response to Re: Overhead cost of Serializable Snapshot Isolation  (Greg Sabino Mullane <greg@endpoint.com>)
Responses Re: Overhead cost of Serializable Snapshot Isolation
Re: Overhead cost of Serializable Snapshot Isolation
List pgsql-hackers
On Tue, Oct 11, 2011 at 9:21 PM, Greg Sabino Mullane <greg@endpoint.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Dumping roles improvements?
Next
From: Josh Berkus
Date:
Subject: Re: COUNT(*) and index-only scans