Re: pg_config wrongly marked as not parallel safe? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_config wrongly marked as not parallel safe?
Date
Msg-id 17826.1543591964@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_config wrongly marked as not parallel safe?  (Joe Conway <mail@joeconway.com>)
Responses Re: pg_config wrongly marked as not parallel safe?  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> On 11/30/18 3:30 AM, Kyotaro HORIGUCHI wrote:
>> # And returning to the topic, I vote for pg_config should be "stable".

> And on that note, Does this change does warrant backpatching, or should
> be applied to master only?

I don't think back-patching the catalog change is really a good idea.
The amount of work involved (e.g. release-noting how to perform the
update on existing databases) is way out of proportion to the benefit
for this particular case.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Flexible permissions for REFRESH MATERIALIZED VIEW
Next
From: Dmitry Dolgov
Date:
Subject: Re: Hash Joins vs. Bloom Filters / take 2