RE: COPY locking

Поиск
Список
Период
Сортировка
От Mikheev, Vadim
Тема RE: COPY locking
Дата
Msg-id 3705826352029646A3E91C53F7189E320165FF@sectorbase2.sectorbase.com
обсуждение исходный текст
Ответ на COPY locking  (John Coers <coers@intrinsity.com>)
Список pgsql-general
> > Probably we could
> > optimize this somehow, but allocation of new page in bufmgr is
> > horrible and that's why we have locks in hio.c from the beginning.
>
> See later message about eliminating lseeks --- I think we should be
> able to avoid doing this lock for every single tuple, as it does now,
> and only do it when we need to allocate a new page.

Please test current/your hio.c versions when multiple users
insert records into the same table.

Vadim

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

Предыдущее
От: John Coers
Дата:
Сообщение: Re: COPY locking
Следующее
От: David Wheeler
Дата:
Сообщение: Re: Custom Constraint