| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json function volatility |
| Date: | 2014-10-17 20:44:09 |
| Message-ID: | CAHyXU0yat7oc-sYmjAS5jpmyNVot+7w11sed_CNjZv_b6_vH0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 17, 2014 at 3:03 PM, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-10-17 20:52:40 | Re: json function volatility |
| Previous Message | Peter Eisentraut | 2014-10-17 20:12:03 | Re: Materialized views don't show up in information_schema |