| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Geoff Winkless <gwinkless(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb problematic operators |
| Date: | 2016-12-12 04:52:50 |
| Message-ID: | 6006.1481518370@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Craig Ringer <craig(at)2ndquadrant(dot)com> writes:
> It's definitely annoying, in both directions. ? wasn't a great choice
> for an operator character but it's logical and was grandfathered over
> from hstore.
It was grandfathered from a lot further back than that. A quick look
into the system catalogs says that core Postgres currently has 21
operators that include "?" in their names. Three of those are the
jsonb operators, and the other 18 have been there since circa 1997.
(Most of them seem to date to Tom Lockhart's commit 3c2d74d2a, but
"<?>" is present in Berkeley Postgres v4r2, released in 1994.)
I do not have a lot of patience with client-side code that's unable
to deal with operator names containing "?". It's not like this
requirement has blindsided anybody in this century.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2016-12-12 04:55:59 | Re: Hash Indexes |
| Previous Message | Amit Kapila | 2016-12-12 04:43:04 | Re: Hash Indexes |