| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-04-09 16:04:35 |
| Message-ID: | 30993.1397059475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> One other point here is that non-default opclasses can't be used in
>> UNIQUE/PRIMARY KEY/EXCLUDE constraints, because there's no place to
>> specify an opclass name in those syntaxes. UNIQUE/PRIMARY KEY don't
>> matter here since these aren't btree opclasses, but is there a
>> use-case for EXCLUDE with any of the supported jsonb operators?
> That sounds like an oversight that could better be fixed in EXCLUDE, no?
Well, there hasn't been a use-case up to now. I'm not sure there's
one yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-09 16:18:51 | Re: Call for GIST/GIN/SP-GIST opclass documentation |
| Previous Message | Alvaro Herrera | 2014-04-09 16:03:36 | Re: Call for GIST/GIN/SP-GIST opclass documentation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-09 16:18:51 | Re: Call for GIST/GIN/SP-GIST opclass documentation |
| Previous Message | Alvaro Herrera | 2014-04-09 16:03:36 | Re: Call for GIST/GIN/SP-GIST opclass documentation |