Re: jsonb and nested hstore

From: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
To: "Peter Geoghegan" <pg(at)heroku(dot)com>
Cc: "Tomas Vondra" <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: jsonb and nested hstore
Date: 2014-03-12 13:20:28
Message-ID: be3e3bb63fd771cec860906610b099a5.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 Březen 2014, 0:51, Peter Geoghegan wrote:
> On Tue, Mar 11, 2014 at 4:41 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> I think that in practice the
>> general recommendation will be that when indexing at the "top level",
>> use jsonb_hash_ops. When indexing nested items, use the more flexible
>> default GIN opclass. That seems like a pretty smart trade-off to me.
>
> By which I mean: index nested items using an expressional GIN index.

I'm still not sure how would that look. Does that mean I'd have to create
multiple GIN indexes - one for each possible key or something like that?
Can you give an example?

regards
Tomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashoke 2014-03-12 13:36:37 Postgresql XML parsing
Previous Message Andres Freund 2014-03-12 13:19:29 Re: db_user_namespace a "temporary measure"