| From: | Larry White <ljw1001(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: JsonB Gin Index is very large; is there a work around? |
| Date: | 2014-08-20 21:17:34 |
| Message-ID: | CAMdbzVi2Carg+ghBq650Z1=r-CJE4zMN8KPd6hMsyG8MhOvDCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ok Thank you.
FWIW, the documents (which I can't share) consist mainly of a long list of
integers in the form {"n":"41515920318427252715"}, so they really are
outliers.
On Wed, Aug 20, 2014 at 5:09 PM, Peter Geoghegan <
peter(dot)geoghegan86(at)gmail(dot)com> wrote:
> On Wed, Aug 20, 2014 at 1:53 PM, Larry White <ljw1001(at)gmail(dot)com> wrote:
> > Is there anyway to index a subset of the data in a JSONB column? I'm
> > thinking of something like declaring certain paths to be indexed?
>
>
> Yes. See the expression index example in the jsonb documentation.
>
> --
> Regards,
> Peter Geoghegan
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soni M | 2014-08-21 01:16:25 | Query planner question |
| Previous Message | Peter Geoghegan | 2014-08-20 21:09:52 | Re: JsonB Gin Index is very large; is there a work around? |