Re: Augment every test postgresql.conf - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Augment every test postgresql.conf
Date
Msg-id 16623.1546141591@sss.pgh.pa.us
Whole thread Raw
In response to Re: Augment every test postgresql.conf  (Noah Misch <noah@leadboat.com>)
Responses Re: Augment every test postgresql.conf  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> Looking more closely, we already have the TEMP_CONFIG variable and apply it to
> everything except TAP suites.  Closing that gap, as attached, is enough.  The
> buildfarm client uses TEMP_CONFIG to implement its extra_config setting, so
> this will cause extra_config to start applying to TAP suites.

Seems reasonable, but it might be a good idea to warn the buildfarm-owners
list before committing.  (Although I guess it wouldn't be hard to check
the buildfarm database to see if anyone is putting anything interesting
into their critters' TEMP_CONFIG.)

Also, if we're to do this, it seems like applying it to back branches
would be helpful --- but will it work in all the back branches?

            regards, tom lane


pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: add_partial_path() may remove dominated path but still in use
Next
From: Chapman Flack
Date:
Subject: Re: Re: tracking owner of extension-managed objects