pgsql: Mark pg_config() stable rather than immutable

From: Joe Conway <mail(at)joeconway(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Mark pg_config() stable rather than immutable
Date: 2019-02-17 14:23:08
Message-ID: E1gvNLY-0007XG-4N@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Mark pg_config() stable rather than immutable

pg_config() has been marked immutable since its inception. As part of a
larger discussion around the definition of immutable versus stable and
related implications for marking functions parallel safe raised by
Andres, the consensus was clearly that pg_config() is stable, since
it could possibly change output even for the same minor version with
a recompile or installation of a new binary. So mark it stable.

Theoretically this could/should be backpatched, but it was deemed to be not
worth the effort since in practice this is very unlikely to cause problems
in the real world.

Discussion: https://postgr.es/m/20181126234521.rh3grz7aavx2ubjv@alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/290e3b77fde9cd063e20d96b1241566a429943de

Modified Files
--------------
src/include/catalog/pg_proc.dat | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-02-17 17:37:52 pgsql: Fix CREATE VIEW to allow zero-column views.
Previous Message Tatsuo Ishii 2019-02-17 11:52:16 pgsql: Doc: remove ancient comment.