Re: json function volatility - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: json function volatility
Date
Msg-id CAHyXU0yat7oc-sYmjAS5jpmyNVot+7w11sed_CNjZv_b6_vH0g@mail.gmail.com
Whole thread Raw
In response to json function volatility  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: json function volatility
Re: json function volatility
List pgsql-hackers
On Fri, Oct 17, 2014 at 3:03 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> Following up something Pavel wrote, I notice that json_agg() and
> json_object_agg() are both marked as immutable, even though they invoke IO
> functions, while json_object is marked stable, even though it does not, and
> can probably be marked as immutable. Mea maxima culpa.
>
> I'm not sure what we should do about these things now. Is it a tragedy if we
> let these escape into the 9.4 release that way?

Is it too late to change them?  Either way, it seems fairly
implausible someone would come up with a case to stick json_agg(), or
any aggregate function really, inside of an index. So it's not exactly
the crime of the century.

merlin



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Materialized views don't show up in information_schema
Next
From: Caleb Welton
Date:
Subject: Issue with mkdtemp() in port.h