Re: proposal: disallow operator "=>" and use it for named parameters

On Tue, Mar 10, 2015 at 11:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Feb 19, 2015 at 3:15 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> I am marking this as Ready For Committer, the patch is trivial and works
>>> as expected, there is nothing to be added to it IMHO.
>>>
>>> The "=>" operator was deprecated for several years so it should not be too
>>> controversial either.
>
>> Committed with a few documentation tweaks.
>
> Was there any consideration given to whether ruleutils should start
> printing NamedArgExprs with "=>"? Or do we think that needs to wait?

I have to admit that I didn't consider that. What do you think? I
guess I'd be tentatively in favor of changing that to match, but I
could be convinced otherwise.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company