On Wed, Jan 23, 2013 at 6:18 PM, Amit Kapila <amit.kap...@huawei.com> wrote: > On Tuesday, January 22, 2013 10:14 PM Fujii Masao wrote: >> When I removed postgresql.auto.conf and restarted the server, >> I got the following warning message. This is not correct because >> I didn't remove "auto.conf.d" from postgresql.conf. What I removed >> is only postgresql.auto.conf. >> >> WARNING: Default "auto.conf.d" is not present in postgresql.conf. >> Configuration parameters changed with SET PERSISTENT command will not >> be effective. > > How about changing it to below message: > > WARNING: File 'postgresql.auto.conf' is not accessible, either file > 'postgresql.auto.conf' or folder '%s' doesn't exist or default "auto.conf.d" > is not present in postgresql.conf. > Configuration parameters changed with SET PERSISTENT command will not be > effective.
Or we should suppress such a warning message in the case where postgresql.auto.conf doesn't exist? SET PERSISTENT creates that file automatically if it doesn't exist. So we can expect that configuration parameters changed with SET PERSISTENT WILL be effective. This warning message implies that the line "include_dir 'auto.conf.d'" must not be removed from postgresql.conf? If so, we should warn that in both document and postgresql.conf.sample? Or we should hard-code so that something like auto.conf.d is always included even when that include_dir directive doesn't exist? Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
