mirror of
https://github.com/postgres/postgres.git
synced 2025-05-06 19:59:18 +03:00
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
This commit is contained in:
parent
69e5247879
commit
290e3b77fd
@ -10433,7 +10433,7 @@
|
||||
|
||||
# pg_config
|
||||
{ oid => '3400', descr => 'pg_config binary as a function',
|
||||
proname => 'pg_config', prorows => '23', proretset => 't', proparallel => 'r',
|
||||
proname => 'pg_config', provolatile => 's', prorows => '23', proretset => 't', proparallel => 'r',
|
||||
prorettype => 'record', proargtypes => '', proallargtypes => '{text,text}',
|
||||
proargmodes => '{o,o}', proargnames => '{name,setting}',
|
||||
prosrc => 'pg_config' },
|
||||
|
Loading…
x
Reference in New Issue
Block a user