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

From Simon Riggs
Subject Re: SSI non-serializable UPDATE performance
Date
Msg-id BANLkTinNnqxcAnWz+xbwGia3hWJ3hXv9zQ@mail.gmail.com
Whole thread Raw
In response to Re: SSI non-serializable UPDATE performance  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Wed, Apr 27, 2011 at 7:15 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Simon Riggs <simon@2ndQuadrant.com> wrote:
>
>> Reading the code, IIUC, we check for RW conflicts after each write
>> but only if the writer is running a serializable transaction.
>
> Correct as far as that statement goes.

Thanks.

I'm surprised by that though, it seems weird.

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


pgsql-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: Re: PostgreSQL Core Team
Next
From: Simon Riggs
Date:
Subject: Re: SSI non-serializable UPDATE performance