Re: Serializable Isolation without blocking

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Serializable Isolation without blocking
Дата
Msg-id 603c8f071001071202m103c12bex8fe203f5e3808ffd@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Serializable Isolation without blocking  (Greg Stark <gsstark@mit.edu>)
Ответы Re: Serializable Isolation without blocking  (Jeff Davis <pgsql@j-davis.com>)
Re: Serializable Isolation without blocking  (Greg Stark <gsstark@mit.edu>)
Список pgsql-hackers
On Thu, Jan 7, 2010 at 2:40 PM, Greg Stark <gsstark@mit.edu> wrote:
> On Thu, Jan 7, 2010 at 11:08 AM, Markus Wanner <markus@bluegap.ch> wrote:
>> Row level locks are very fine grained, but those are spilled to disk in
>> its current implementation. So those are an even worse fit for the needs
>> of SIREAD.
>
> I think we're still talking past the issue. Predicate locks are not
> row level, nor page level, nor table level.

They're not?  They're just floating out in space somewhere?  There are
several possible ways to implement predicate locks, but every possible
method I can think of involves attaching them at one of those places.

> And how do you do that without tying the implementation to specific
> details of how our planner, table scans, and index access methods
> work?

You don't.  You add additional methods to the index AMs to support
predicate locks, just lilke we do when we want them to support
anything else (bitmap index scans, index-only scans, etc.).

...Robert


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

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: PostgreSQL 8.5 Open Items
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Hot Standy introduced problem with query cancel behavior