Re: location of the configuration files - Mailing list pgsql-hackers
From | mlw |
---|---|
Subject | Re: location of the configuration files |
Date | |
Msg-id | 3E4BECAF.4070404@mohawksoft.com Whole thread Raw |
In response to | Re: location of the configuration files (Bruce Momjian <pgman@candle.pha.pa.us>) |
Responses |
Re: location of the configuration files
Re: location of the configuration files |
List | pgsql-hackers |
<br /><br /> Bruce Momjian wrote:<br /><blockquote cite="mid200302131845.h1DIjRH01532@candle.pha.pa.us" type="cite"><prewrap="">Oliver Elphick wrote: </pre><blockquote type="cite"><pre wrap="">On Thu, 2003-02-13 at 17:52, VinceVielhaber wrote: </pre><blockquote type="cite"><pre wrap="">Seems to me that if FHS allows such a mess, it's reasonenough to avoid compliance. Either that or those of you who build for distributions are making an ill advised change. Simply because the distribution makes the decision to add PostgreSQL, or some other package, to it's distribution doesn't make it a requirement to change the location of the config files. </pre></blockquote><pre wrap="">Debian (andFHS) specifically requires that. All configuration files MUST be under /etc; the reason is to make the system administrator's job easier. Part of the raison d'etre of a distribution is to rationalise the idiosyncrasies of individual projects. The locations used by locally-built packages are up to the local administrator, but they really should not be in /etc and are recommended to be under /usr/local. I really don't see why there is such a not-invented-here mentality about this issue. I say again, standards-compliance is the best way. It makes life easier for everyone if standards are followed. Don't we pride ourselves on being closer to the SQL spec than other databases? Any way, if PostgreSQL stays as it is, I will continue to have to ensure that initdb creates symlinks to /etc/postgresql/, as happens now. </pre></blockquote><pre wrap=""> It doesn't have anything to do with "not-invented-here", which is a common refrain by people who don't like our decisions, like "Why don't you use mmap()? Oh, it's because I thought of it and you didn't". Does anyone seriously believe that is the motiviation of anyone in this project! I certainly don't. Now, on to this configuration discussion. Seems moving the config file out of $PGDATA requies either:1) we specifiy both the config directory and the data directory onpostmaster start2) we specifythe pgdata directory inside postgresql.conf orother config file Is this accurate? </pre></blockquote> The patch that I have adds three settings to postgresql.conf and one command line parameter.<br/><br /> hba_conf = 'filename'<br /> ident_conf='filename'<br /> data_dir='path'<br /><br /> The command linaeparameter is -C, used as:<br /><br /> postmaster -C /usr/local/etc/postgresql.conf<br /><br /> I think this will helpadministrators. <br /><br /> Bruce, can you shed some light as to why this is being so strongly rejected. I just don'tsee any downside. I just don't get it. <br /><br /> I will be resubmitting my patch for the 7.3.2 tree.<br /><br /><br/><blockquote cite="mid200302131845.h1DIjRH01532@candle.pha.pa.us" type="cite"><pre wrap=""> </pre></blockquote><br/>
pgsql-hackers by date: