Re: determine snapshot after obtaining locks for first statement

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: determine snapshot after obtaining locks for first statement
Дата
Msg-id 603c8f070912170706o57161394ie68f672c4da09bf6@mail.gmail.com
обсуждение исходный текст
Ответ на Re: determine snapshot after obtaining locks for first statement  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: determine snapshot after obtaining locks for first statement  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
On Thu, Dec 17, 2009 at 10:05 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> "Markus Wanner" <markus@bluegap.ch> wrote:
>
>> Another line of thought: isn't this like READ COMMITTED for just
>> the first operation in a SERIALIZABLE transaction?
>
> I've mulled it over and I have two different logical proofs that
> this is safe; if anyone is dubious I'd be happy to share.
>
> This seems likely to be of significant benefit in some workloads,
> and I can't see anywhere that it is likely to cost much.  Any
> objections to adding this to the TODO list as a performance item?

I thought you concluded two emails ago that it wouldn't work for PG?
It's certainly not clear to me what exactly the TODO would be.

...Robert


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: determine snapshot after obtaining locks for first statement
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: determine snapshot after obtaining locks for first statement