| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Craig Ringer <craig(at)2ndquadrant(dot)com>, 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-13 18:25:11 |
| Message-ID: | 20158.1481653511@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nico Williams <nico(at)cryptonector(dot)com> writes:
> On Tue, Dec 13, 2016 at 10:26:24AM +0900, Michael Paquier wrote:
>> On Mon, Dec 12, 2016 at 10:22 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>>> One option might be for Postgres to define duplicate operator names
>>> using ¿ or something else.
>> Are you sure that using a non-ASCII character is a good idea for an
>> in-core operator? I would think no.
> Eventually language designers will cross that Rubicon in mainstream
> languages. And why not?
Because it will create all sorts of character-set-conversion hazards.
In the current design of Postgres it flat out would not work, because
template0 has to be encoding-agnostic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ronan.dunklau | 2016-12-13 18:39:23 | Re: New design for FK-based join selectivity estimation |
| Previous Message | Robert Haas | 2016-12-13 18:10:21 | Re: Declarative partitioning - another take |