Re: SPGist "triple parity" concept doesn't work

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: SPGist "triple parity" concept doesn't work
Дата
Msg-id
15703.1371234518@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Alvaro Herrera <alvherre@2ndquadrant.com>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Greg Stark <stark@mit.edu>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Will Crawford <billcrawford1970@gmail.com>
Teodor Sigaev  writes:
>> Anyway I now think that we might be better off with the other idea of
>> abandoning an insertion and retrying if we get a lock conflict.

> done, look at the patch.

Looks good, committed with some cosmetic adjustments.

> We definetly need new idea of locking protocol and I'll return to this
> problem at autumn (sorry, I havn't time in summer to do this
> research).

OK.  I think the performance of this way will be okay, actually, in most
cases anyhow.  It'll do till we have a better idea.
		regards, tom lane


В списке pgsql-hackers по дате отправления
От: Joshua D. Drake
Дата:
От: Fabien COELHO
Дата:
FAQ