The forgotten assignment operator “=” and the commonplace “:=”

by

In PL/PgSQL parser, assignment operator is defined as 

assign_operator : '='
                | COLON_EQUALS
                ;

This is a legacy feature, present in source code since 1998, when it was introduced – as we can see in the PostgreSQL Git repo.

Starting from version 9.4 it is oficially documented.

This idiosyncrasy – of having two operators for same thing – was raised on pgsql users list, and some people requested it to be removed, but it’s still kept in the core because fair corpus of legacy code relies on it.

See this message from Tom Lane (core Pg developer).

So, to answer your questions straight:

Didn’t I find some section in the docs which mention and/or explains
this?

You did not find it because it was undocumented, which is fixed as of version 9.4.

Are there any known consequences using = instead of :=.

There are no side consequences of using =, but you should use := for assignment to make your code more readable, and (as a side effect) more compatible with PL/SQL.

Update: there may be a side consequence in rare scenarios (see Erwin’s answer)

UPDATE: answer updated thanks to input from Daniel, Sandy & others.

More Related Contents:

  1. What are ‘$$’ used for in PL/pgSQL
  2. INSERT with dynamic table name in trigger function
  3. Truncating all tables in a Postgres database
  4. PostgreSQL: ERROR: 42601: a column definition list is required for functions returning “record”
  5. How to set value of composite variable field using dynamic SQL
  6. How do I do large non-blocking updates in PostgreSQL?
  7. Execute a dynamic crosstab query
  8. Is there a way to disable function overloading in Postgres
  9. Can I make a plpgsql function return an integer without using a variable?
  10. PostgreSQL function returning multiple result sets
  11. Dynamic SQL (EXECUTE) as condition for IF statement
  12. Returning from a function with OUT parameter
  13. SELECT raises exception in PL/pgSQL function
  14. Test for null in function with varying parameters
  15. Return SETOF rows from PostgreSQL function
  16. Error when setting n_distinct using a plpgsql variable
  17. Postgres FOR LOOP
  18. Dynamically generate columns for crosstab in PostgreSQL
  19. Function to loop through and select data from multiple tables
  20. PL/pgSQL functions: How to return a normal table with multiple columns using an execute statement
  21. SQL Sub queries in check constraint
  22. Cursor based records in PostgreSQL
  23. ERROR: unterminated quoted string at or near
  24. How can I send some http request from postgresql function or trigger
  25. Select from a table variable
  26. Hashing a String to a Numeric Value in PostgreSQL
  27. Loop on tables with PL/pgSQL in Postgres 9.0+
  28. plpgsql error “RETURN NEXT cannot have a parameter in function with OUT parameters” in table-returning function
  29. Loop through columns of RECORD
  30. Format specifier for integer variables in format() for EXECUTE?

Leave a Comment