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

Поиск
Список
Период
Сортировка
От Teodor Sigaev
Тема Re: SPGist "triple parity" concept doesn't work
Дата
Msg-id 51BB094C.2020209@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  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> 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.

I was faced with the fact that my mail is considered spam by postgresql.org, so
I repeat some hthoughts from previous mail:

I considered the idea to forbid placement of child on the same page as parent,
but this implementation a) could significantly increase size of index, b)
doesn't solve Greg's point.

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).

--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/

Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Issue with PGC_BACKEND parameters
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [PATCH] Add transforms feature