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 4136ffa0905281612w40895bcdw644a7831e80ac454@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
List pgsql-hackers
On Thu, May 28, 2009 at 11:49 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> The problem
> is that the cost of a "perfect" predicate locking system is much
> higher than the cost of letting some transaction block or roll back
> for retry.

Surely that depends on how expensive it is to retry the transaction?
Like, how much would it suck to find your big data load abort after 10
hours loading data? And how much if it didn't wasn't even selecting
data which your data load conflicted with.

-- 
greg


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Next
From: Joshua Tolley
Date:
Subject: Re: Dtrace probes documentation