Re: SSI non-serializable UPDATE performance - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: SSI non-serializable UPDATE performance
Date
Msg-id BANLkTi=DVO4MV1pa8==e2ka1Bgwg-vN+qw@mail.gmail.com
Whole thread Raw
In response to Re: SSI non-serializable UPDATE performance  (Dan Ports <drkp@csail.mit.edu>)
Responses Re: SSI non-serializable UPDATE performance  (Dan Ports <drkp@csail.mit.edu>)
Re: SSI non-serializable UPDATE performance  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Mon, Apr 25, 2011 at 4:33 AM, Dan Ports <drkp@csail.mit.edu> wrote:
> On Sat, Apr 23, 2011 at 08:54:31AM -0500, Kevin Grittner wrote:
>> Even though this didn't show any difference in Dan's performance
>> tests, it seems like reasonable insurance against creating a new
>> bottleneck in very high concurrency situations.
>>
>> Dan, do you have a patch for this, or should I create one?
>
> Sure, patch is attached.


Reading the code, IIUC, we check for RW conflicts after each write but
only if the writer is running a serializable transaction.

Am I correct in thinking that there is zero impact of SSI if nobody is
running a serializable transaction?


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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: timeline garbage in pg_basebackup (was gcc 4.6 warnings -Wunused-but-set-variable)
Next
From: Josh Berkus
Date:
Subject: Re: "stored procedures" - use cases?