Re: User-facing aspects of serializable transactions - Mailing list pgsql-hackers

From Greg Stark
Subject Re: User-facing aspects of serializable transactions
Date
Msg-id 4136ffa0905280857j79013e72g9cb15f829b703ed@mail.gmail.com
Whole thread Raw
In response to Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Thu, May 28, 2009 at 4:33 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
>
> Can you cite anywhere that such techniques have been successfully used
> in a production environment

Well there's a reason our docs say: "Such a locking system is complex
to implement and extremely expensive in execution"

> or are you suggesting that we break new
> ground here?  (The techniques I've been assuming are pretty well-worn
> and widely used.)

Well they're well-worn in very different databases which have much
less flexibility in how they access data. In part that inflexibility
comes *from* their decision to implement transaction isolation using
locks and to tie those locks to the indexing infrastructure.

--
greg


pgsql-hackers by date:

Previous
From: "Markus Wanner"
Date:
Subject: Re: PostgreSQL Developer meeting minutes up
Next
From: Tom Lane
Date:
Subject: Re: Compiler warning cleanup - unitilized const variables, pointer type mismatch