Re: Serializable Isolation without blocking

Поиск
Список
Период
Сортировка
От Albe Laurenz
Тема Re: Serializable Isolation without blocking
Дата
Msg-id D960CB61B694CF459DCFB4B0128514C202FF65B3@exadv11.host.magwien.gv.at
обсуждение исходный текст
Ответ на Re: Serializable Isolation without blocking  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: Serializable Isolation without blocking  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
Kevin Grittner wrote:
> > Where does T1 select rows that were modified by T0? It selects only
> > one row, the one it modified itself, right?
>
> You have to select it to know whether to count it, right?

We are getting closer.

So an SIREAD lock is taken for every row that is examined during
the execution of an execution plan?

Ah.

What if there is an index on the "ishighlander" row?
Then an index scan would find only one candidate to examine,
and the other rows would not even be touched by the execution plan.
Then how would they contract an SIREAD lock?

Yours,
Laurenz Albe


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

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Serializable Isolation without blocking
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [BUGS] BUG #4796: Recovery followed by backup creates unrecoverable WAL-file