On Wednesday, October 31, 2012 3:25 AM Josh Berkus > > I should think that doing this requires heading back towards there > > being a single unique configuration stream, and over the course of > > several versions, deprecating the INCLUDE directive. > > Oh, maybe I should take a closer look at Amit's proposal then. I > thought we planned to make use of the INCLUDE facility for SET > PERSISTENT, including supporting include-if-exists. Possibly what he's > proposing and what I thought our last consensus were are highly > divergent.
Currently INCLUDE is used for including postgresql.conf.auto in postgresql.conf by default. Can you please let me know what is the expectation? Instead of INCLUDE, 1. include-if-exists can be used. 2. In code first read .auto file then .conf and override the values read from .auto by values from .conf. With Regards, Amit Kapila. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
