Re: User-facing aspects of serializable transactions
| От | Kevin Grittner |
|---|---|
| Тема | Re: User-facing aspects of serializable transactions |
| Дата | |
| Msg-id | 4A1D9BC3.EE98.0025.1@wicourts.gov обсуждение исходный текст |
| Ответ на | Re: User-facing aspects of serializable transactions (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: User-facing aspects of serializable transactions
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> wrote: > I think we should introduce a new value for SET TRANSACTION ISOLATION > LEVEL, maybe SNAPSHOT, intermediate between READ COMMITTED and > SERIALIZABLE. 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? -Kevin
В списке pgsql-hackers по дате отправления: