Re: jsonb concatenate operator's semantics seem questionable

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ilya Ashchepkov <koctep(at)gmail(dot)com>
Subject: Re: jsonb concatenate operator's semantics seem questionable
Date: 2015-05-18 00:46:01
Message-ID: 1BB4CADB-1D6F-4427-9F38-D6FACCE74246@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On May 17, 2015, at 8:38 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> The current behavior does not seem acceptable for the concatenate
> operator ("operator || jsonb").

I don't agree. It seems pretty clear to me after reading the new posts that the behavior is not an oversight, and that's enough for me to say that we should leave this alone.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-05-18 00:53:57 Re: jsonb concatenate operator's semantics seem questionable
Previous Message Robert Haas 2015-05-18 00:39:54 Re: WALWriteLock contention