Re: IMMUTABLE and PARALLEL SAFE function markings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: IMMUTABLE and PARALLEL SAFE function markings
Date
Msg-id 29466.1543278855@sss.pgh.pa.us
Whole thread Raw
In response to Re: IMMUTABLE and PARALLEL SAFE function markings  (Vik Fearing <vik.fearing@2ndquadrant.com>)
List pgsql-hackers
FWIW, I'm inclined to think that pg_config should be marked as stable
not immutable.  Aside from the minor-version-upgrade issue, what if
you install new binaries that are the same version but built with
different configure flags?

The pg_config outputs are roughly as stable as initdb-inserted
catalog data, and we've never judged that functions that return
catalog data can be marked immutable.

There seems no reason it can't be parallel safe, though, since
worker processes should get the same answers as their parent.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_config wrongly marked as not parallel safe?
Next
From: Stephen Frost
Date:
Subject: Re: IMMUTABLE and PARALLEL SAFE function markings