Re: Different behaviour of concate() and concate operator || - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Different behaviour of concate() and concate operator ||
Date
Msg-id CAM-w4HOeedq7fDLkxyPHLuB3f=+dT-Azt=27krPzAf0BhPjh=Q@mail.gmail.com
Whole thread Raw
In response to Re: Different behaviour of concate() and concate operator ||  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Different behaviour of concate() and concate operator ||  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
The missing bit of context is that concat() is there because early on
in Postgres's life there was an effort to have a full suite of Oracle
compatibility functions. If someone suggested it now they would be
pushed towards making it an extension or pointed at EDB. But things
like concat are the remnants of that.



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Planned downtime @ Rackspace
Next
From: Tom Lane
Date:
Subject: Re: includedir_internal headers are not self-contained