Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think we should introduce a new value for SET TRANSACTION
> LEVEL, maybe SNAPSHOT, intermediate between READ COMMITTED and
The standard defines such a level, and calls it REPEATABLE READ.
Snapshot semantics are more strict than required for that level, which
is something you are allowed to get when you request a given level, so
it seems clear to me that when you request REPEATABLE READ mode, you
should get our current snapshot behavior. I'm not clear on what the
benefit would be of aliasing that with SNAPSHOT. If there is a
benefit, fine; if not, why add it?
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2009-05-28 01:00:53|
|Subject: Re: User-facing aspects of serializable transactions|
|Previous:||From: Tom Lane||Date: 2009-05-28 00:55:18|
|Subject: Re: User-facing aspects of serializable transactions |