Re: BUG #6165: documentation bug in plpgsql-declarations.html and plpgsql-statements.html (or plpgsql parser bug) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6165: documentation bug in plpgsql-declarations.html and plpgsql-statements.html (or plpgsql parser bug)
Date
Msg-id 9622.1314044224@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6165: documentation bug in plpgsql-declarations.html and plpgsql-statements.html (or plpgsql parser bug)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #6165: documentation bug in plpgsql-declarations.html and plpgsql-statements.html (or plpgsql parser bug)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Aug 17, 2011 at 1:21 AM, raf <raf@raf.org> wrote:
>> so, there is either a plpgsql parser bug that treats the sql equality
>> operator as the plpgsql assignment operator, or "=" is an undocumented
>> alternative to the documented plpgsql assignment operator (":=").

> I think it's the latter.

It's definitely intentional, not a bug, so far as the source code is
concerned:

assign_operator : '='
                | COLON_EQUALS
                ;

> I have a vague recollection that we might
> have left that undocumented on purpose, but I'm not actually sure why
> we support it in the first place.

I think it's legacy at this point.  We have discussed before whether to
document it, and IIRC the general feeling was "if we do document it,
we'll never be able to get rid of it".  Whether we could get rid of it
now (instead of documenting it) was not seriously discussed.  I've seen
at least a few people saying that they do rely on it ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #5963: make -j4 check fails
Next
From: "Eduard Rozenberg"
Date:
Subject: BUG #6175: Service name should be fixed