From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-03-31 16:34:39 |
Message-ID: | CA+TgmoZXt8f5d21joe7wzNViGbmo5vvnOGD0GWc5XzdLYNjxPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 14, 2014 at 9:17 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 03/14/2014 06:44 PM, Tomas Vondra wrote:
>> Stupid question - so if I have a json like this:
>
> Not a stupid question, actually. In fact, I expect to answer it 400 or
> 500 times over the lifespan of 9.4.
>
>> { "a" : { "b" : "c"}}
>>
>> the GIN code indexes {"b" : "c"} as a single value? And then takes "c"
>> and indexes it as a single value too?
>
> I don't know that "c" is indexed separately.
>
>> Because otherwise I don't understand how the index could be used for
>> queries with @> '{"a" : {"b" : "c"}}' conditions (i.e. path "[a,b]" with
>> value "c").
>>
>> Hmmmm, if that's how it works, removing the size limit would be
>> certainly more difficult than I thought.
>
> Precisely. Hence, the Russian plans for VODKA.
Have these plans been shared publicly somewhere? Got a link?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-03-31 16:41:44 | Re: HEAD seems to generate larger WAL regarding GIN index |
Previous Message | Alvaro Herrera | 2014-03-31 16:33:13 | Re: PQputCopyData dont signal error |