Re: User-facing aspects of serializable transactions

Поиск
Список
Период
Сортировка
От Jeff Davis
Тема Re: User-facing aspects of serializable transactions
Дата
Msg-id 1243470036.24838.168.camel@monkey-cat.sm.truviso.com
обсуждение исходный текст
Ответ на Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы 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>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: search_path vs extensions
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: search_path vs extensions