Re: jsonb and nested hstore

From: Oleg Bartunov <obartunov(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Tomas Vondra <tv(at)fuzzy(dot)cz>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-03-12 20:34:52
Message-ID: CAF4Au4wzY0TtLkyxqF1c_chxhGrXTN-i7aX1kwchP8_jjGTn_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 13, 2014 at 12:10 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Wed, Mar 12, 2014 at 11:57 AM, Oleg Bartunov <obartunov(at)gmail(dot)com> wrote:
>> Also, GiST index is faster for create/update operations. I really hope we will
>> improve jsonb indexing in the next one-two releases. For now I'd suggest people
>> index expressional indexes to index just interesting keys or use GiST.
>
> When do you ever want to index non-interesting keys?

Regular user may just index all keys.

I mean, that json can contains keys, which are not searched, so it's
not needed to index them and save index size. We probably could
provide option in CREATE INDEX to specify what to index and what not
index, but it require planner to know that information.

>
> --
> Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-03-12 20:37:39 Re: jsonb and nested hstore
Previous Message Josh Berkus 2014-03-12 20:34:47 Re: Replication slots and footguns