Re: json function volatility

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: json function volatility
Date: 2014-10-17 20:52:40
Message-ID: CAM3SWZRyNSSfq3g7j78sRqOr49XaJJGww4HwfbSv9Vrtz2GULQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 17, 2014 at 1:44 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> 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.

Indexes reject aggregates outright as acceptable expressions for
indexing. That's not the only issue, of course.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-10-17 20:59:49 Re: json function volatility
Previous Message Merlin Moncure 2014-10-17 20:44:09 Re: json function volatility