Re: postgresql.auto.conf read from wrong directory - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: postgresql.auto.conf read from wrong directory
Date
Msg-id 20140616085509.GA6964@msg.df7cb.de
Whole thread Raw
In response to Re: postgresql.auto.conf read from wrong directory  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Re: Amit Kapila 2014-06-16 <CAA4eK1++wcFswhzH=92qiQFB=C0_Uy=mReadvHZXdrF3JOWX6A@mail.gmail.com>
> Developer options are mainly for debugging information or might help in one
> of the situations, so I thought somebody might not want them to be part of
> server configuration once they are set.  We already disallow parameters like
> config_file, transaction_isolation, etc. which are disallowed to be set in
> postgresql.conf.  Could you please explain me a bit in which
> situations/scenarios, do you think that allowing developer options via Alter
> System can be helpful?

Oh if these are disallowed in postgresql.conf, they should be
disallowed in auto.conf too. I meant to say that there shouldn't be
additional restrictions for auto.conf, except for cases like
data_directory which won't work at all (or are highly confusing).

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/



pgsql-hackers by date:

Previous
From: Shigeru Hanada
Date:
Subject: Re: [v9.5] Custom Plan API
Next
From: xbzhang
Date:
Subject: How to implement the skip errors for copy from ?