| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "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-04-09 16:51:43 |
| Message-ID: | CAM3SWZQ2Pd9d7Ae3BbjyqZ5=FD+3FMaNcer9bG=xHAufbsqdPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Wed, Apr 9, 2014 at 8:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Maybe we should make *neither* of these the default opclass, and give
>> *neither* the name json_ops.
>
> There's definitely something to be said for that. Default opclasses are
> sensible when there's basically only one behavior that's interesting for
> most people. We can already see that that's not going to be the case
> for jsonb indexes, at least not with the currently available alternatives.
I've heard worse ideas.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-04-09 18:22:54 | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| Previous Message | Tom Lane | 2014-04-09 16:18:51 | Re: Call for GIST/GIN/SP-GIST opclass documentation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-09 16:57:27 | Re: [PATCH] Add transforms feature |
| Previous Message | Emre Hasegeli | 2014-04-09 16:43:23 | Re: GiST support for inet datatypes |