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

From Jeff Davis
Subject Re: User-facing aspects of serializable transactions
Date
Msg-id 1243470036.24838.168.camel@monkey-cat.sm.truviso.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  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Wed, 2009-05-27 at 18:54 -0500, Kevin Grittner wrote:
> I've gotten the distinct impression that some would prefer to continue
> to use their existing techniques under snapshot isolation.  I was sort
> of assuming that they would want a GUC to default to legacy behavior
> with a new setting for standard compliant behavior.

That sounds like the "migration path" sort of GUC, which sounds
reasonable to me.

But what about all the other possible behaviors that were brought up
(mentioned in more detail in [1]), such as:

1. implementation of the paper's technique sans predicate locking, that
would avoid more serialization anomalies but not all?
2. various granularities of predicate locking?

Should these be things the user controls per-transaction? If so, how?

Regards,Jeff Davis

[1] http://archives.postgresql.org/pgsql-hackers/2009-05/msg01128.php



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: search_path vs extensions
Next
From: Andrew Dunstan
Date:
Subject: Re: search_path vs extensions