pgsql: Correct volatility markings of a few json functions.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Correct volatility markings of a few json functions.
Date: 2014-10-20 19:30:15
Message-ID: E1XgIel-00084p-Vk@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Correct volatility markings of a few json functions.

json_agg and json_object_agg and their associated transition functions
should have been marked as stable rather than immutable, as they call IO
functions indirectly. Changing this probably isn't going to make much
difference, as you can't use an aggregate function in an index
expression, but we should be correct nevertheless.

json_object, on the other hand, should be marked immutable rather than
stable, as it does not call IO functions.

As discussed on -hackers, this change is being made without bumping the
catalog version, as we don't want to do that at this stage of the cycle,
and the changes are very unlikely to affect anyone.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/6e0a053a963024698de8ba315eed7455520d1a92

Modified Files
--------------
src/include/catalog/pg_proc.h | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2014-10-20 19:31:13 pgsql: Correct volatility markings of a few json functions.
Previous Message Tom Lane 2014-10-20 16:24:03 pgsql: Fix mishandling of FieldSelect-on-whole-row-Var in nested latera