From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
Date: | 2014-04-09 08:40:39 |
Message-ID: | CAM3SWZQbjqippSdQU2RHFTOe_SyoMcH_MOCcUeYPA0NWPjYqLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Wed, Apr 9, 2014 at 1:21 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> I didn't say that. On the contrary, I think the shotgun approach jsonb_ops
> and jsonb_hash_ops take is too broad. It should be possible to specify what
> to index in a more detailed fashion.
It is - use an expression index. That's by far the most important way
to specify what to index in a more detailed fashion. There are others,
but that's the major one. Beyond that, yes, it's necessary to
carefully write your query predicate a certain way. However, a similar
situation exists in MongoDB, where there is a distinction between
"Indexes on embedded fields" (which must be accessed using special
"dot notation") and "indexes on subdocuments" (which cannot be
accessed using "dot notation"). It's late here, but I'm pretty sure
that's a feature and not a limitation.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tomáš Greif | 2014-04-09 12:17:34 | Add link to partial unique index from Constraints (5.3) |
Previous Message | Bruce Momjian | 2014-04-09 08:25:56 | Re: interval data type storage size |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-04-09 09:34:42 | Re: [RFC, POC] Don't require a NBuffer sized PrivateRefCount array of local buffer pins |
Previous Message | Bruce Momjian | 2014-04-09 08:35:21 | Re: ipc_test |