Re: jsonb and nested hstore
| От | Alexander Korotkov |
|---|---|
| Тема | Re: jsonb and nested hstore |
| Дата | |
| Msg-id | CAPpHfdt3K4mt4rBEAQPOAGFx1-WtrVTZR58kxPiyV-0w3GTNeg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: jsonb and nested hstore (Peter Geoghegan <pg@heroku.com>) |
| Ответы |
Re: jsonb and nested hstore
|
| Список | pgsql-hackers |
I've noticed two commits on github.
commit b8199ee3c2506ab81b47a0b440363fc90c0d6956
Author: Peter Geoghegan <pg@heroku.com>
Date: Wed Mar 19 02:02:16 2014 -0700
For jsonb_hash_ops, hash less
By limiting the GIN entries to the least-nested level, the delicious.com
sample JSON dataset index shrinks in size from 382MB to 255MB without
any apparent downside.
commit 2cea5213dba011625fc0d5c6b447e838080087b1
Author: Peter Geoghegan <pg@heroku.com>
Date: Wed Mar 19 02:13:42 2014 -0700
Revert "For jsonb_hash_ops, hash less"
This might be workable with another approach, but leave it for now. This
reverts commit b8199ee3c2506ab81b47a0b440363fc90c0d6956.
Besides implementation, what the idea was here? For me, it's impossible to skip any single element, because it's possible for query to include only this element. If we skip that element, we can't answer corresponding query no more.
With best regards,
Alexander Korotkov.
В списке pgsql-hackers по дате отправления: