| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, depesz(at)depesz(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why are JSON extraction functions STABLE and not IMMUTABLE? |
| Date: | 2013-04-15 23:55:28 |
| Message-ID: | 20130415235528.GC5343@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 15, 2013 at 04:41:53PM -0400, Andrew Dunstan wrote:
>
> On 04/15/2013 11:46 AM, Andres Freund wrote:
> >>
> >>Me either. It's an oversight, really. Unless there is any objection I'll
> >>change them toot sweet. What about the existing (as of 9.2) functions?
> >ISTM json_in, out, recv, send should also be immutable. array_to_json,
> >row_to_json et all can't be tho.
>
>
> OK, although these have been like this since 9.2. I'm not sure why
> json_out is immutable but json_in isn't.
>
> Does changing these require a catalog version bump?
Yes.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-04-16 03:57:03 | event trigger API documentation? |
| Previous Message | Rodrigo Barboza | 2013-04-15 22:59:01 | Re: Query not using index for user defined type |