| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Enhanced ALTER OPERATOR |
| Date: | 2015-05-20 18:40:38 |
| Message-ID: | 20150520184037.GC5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-20 18:41:08 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Andrew Dunstan | 2015-05-20 18:34:17 | Re: jsonb concatenate operator's semantics seem questionable |