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+U5nMJY1rverLx=QN=ZfZg1AVRFAuCeMgkHg7himVMXbc8hPw@mail.gmail.com
Whole thread Raw
In response to Re: Overhead cost of Serializable Snapshot Isolation  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Overhead cost of Serializable Snapshot Isolation  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Tue, Oct 11, 2011 at 10:00 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Simon Riggs <simon@2ndQuadrant.com> wrote:
>
>> "You'll have to retest your apps" just isn't a good answer
>
> For which major PostgreSQL releases have you recommended that people
> deploy their apps without retesting?

None. People don't always follow my advice, regrettably. They ask
comparative questions like "What is the risk of upgrade?", "How much
testing is required?"

I never met a customer yet that has an automated test suite designed
to stress the accuracy of results under concurrent workloads, so the
inability to control the way a new feature operates makes such
questions more likely to be given an answer that indicates greater
effort and higher risk. That is exactly what I personally would wish
to avoid.

An off switch encourages people to use new features. It is not a
punishment or an admonition to the developer.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Overhead cost of Serializable Snapshot Isolation
Next
From: Florian Pflug
Date:
Subject: Re: Overhead cost of Serializable Snapshot Isolation