Re: Proposal: GiST constraints
| От | Teodor Sigaev |
|---|---|
| Тема | Re: Proposal: GiST constraints |
| Дата | |
| Msg-id | 484E7AA9.80003@sigaev.ru обсуждение исходный текст |
| Ответ на | Re: Proposal: GiST constraints (Jeff Davis <pgsql@j-davis.com>) |
| Ответы |
Re: Proposal: GiST constraints
|
| Список | pgsql-hackers |
> This can be solved by my proposal, but I just don't know how it would > apply to something like GIN, for instance. It could replace the unique Hmm, your proposal isn't applicable to GIN, because GIN stores a lot of keys for only one value to be indexed. > being inserted by other concurrent transactions, and those values can > be variable in size. What other mechanism do we have to share those > variable-sized values among several backends? In theory, any indexed value in index (for GiST, after compression) should fit into page at least. -- Teodor Sigaev E-mail: teodor@sigaev.ru WWW: http://www.sigaev.ru/
В списке pgsql-hackers по дате отправления: