| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| Date: | 2014-05-10 21:00:54 |
| Message-ID: | 536E9386.6050701@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 05/10/2014 04:42 PM, Heikki Linnakangas wrote:
>
>
> The main difference between the two opclasses from a user's standpoint
> is not whether they hash or not. The big difference is that one
> indexes complete paths from the root, and the other indexes just the
> "leaf" level. For example, if you have an object like '{"foo": {"bar":
> 123 } }', one will index "foo", "foo->bar", and "foo->bar->123" while
> the other will index "foo", "bar" and "123".
>
> Whether the opclasses use hashing to shorten the key is an orthogonal
> property, and IMHO not as important. To reflect that, I suggest that
> we name the opclasses:
>
> json_path_ops
> json_value_ops
>
> or something along those lines.
>
>
That looks like the first suggestion I've actually liked and that users
will be able to understand.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2014-05-10 21:03:24 | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| Previous Message | Heikki Linnakangas | 2014-05-10 20:42:34 | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2014-05-10 21:02:23 | Re: New pg_lsn type doesn't have hash/btree opclasses |
| Previous Message | Heikki Linnakangas | 2014-05-10 20:43:06 | Re: Lossy bitmap scan is broken in GIN |