| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Enhanced ALTER OPERATOR |
| Date: | 2015-05-20 18:44:14 |
| Message-ID: | 1254.1432147454@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Uriy Zhuravlev wrote:
>> And can you explain more about the syntax?
> I think he means to treat COMMUTATOR etc like a generic element list,
> i.e. don't define new keywords in kwlist.h/gram.y at all but rather pass
> the names as strings (probably using a list of DefElem) and strcmp()
> them in OperatorUpd() or something.
Yeah. If they aren't keywords in CREATE OPERATOR, I don't think they
should be in ALTER OPERATOR either. Indeed, the syntax of the two
commands probably ought to be similar.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-20 18:50:41 | Re: WIP: Enhanced ALTER OPERATOR |
| Previous Message | Ryan Pedela | 2015-05-20 18:42:38 | Re: jsonb concatenate operator's semantics seem questionable |