Horton

Re: SSI non-serializable UPDATE performance

Dan Ports <drkp@csail.mit.edu>

View thread
From: Dan Ports <drkp@csail.mit.edu>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-04-27T17:59:14Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add fast paths for cases when no serializable transactions are running.

On Wed, Apr 27, 2011 at 06:26:52PM +0100, Simon Riggs wrote:
> 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?

That is correct, now.

(Well, other than having to check whether a serializable transaction is
running, the cost of which is truly negligible.)

Dan

-- 
Dan R. K. Ports              MIT CSAIL                http://drkp.net/