From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Ryan Pedela <rpedela(at)datalanche(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(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-22 19:44:20 |
Message-ID: | 555F8714.2020006@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/22/2015 03:27 PM, Peter Geoghegan wrote:
> On Fri, May 22, 2015 at 11:59 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> As for raising an error, in principle it's doable, but the code to detect it
>> might get messy. Also, I don't want a huge number of knobs. So I'm excited
>> about the idea.
> I think that that's a bad default behavior, although I don't think
> that's what Jim means. Consider our experience with having subscript
> operators throw errors -- it complicates certain cases (my complaint
> at the time was about expression indexes, but there are others).
>
I certainly agree about indexable operations. However this seems
unlikely to be indexed, although I'm prepared to be educated on that point.
Still I'd rather not add yet another parameter to the function, and I
certainly don't want to make throwing an error the only behaviour.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Ridge | 2015-05-22 20:08:40 | Re: Change pg_cancel_*() to ignore current backend |
Previous Message | Peter Geoghegan | 2015-05-22 19:27:40 | Re: jsonb concatenate operator's semantics seem questionable |