Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
От | Greg Stark |
---|---|
Тема | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Дата | |
Msg-id | CAM-w4HN7ZUTOi4EsbgP5D0cpXJa4_TpAaa1yjEkfevAgKQptwA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Re: ALTER SYSTEM SET command to change postgresql.conf
parameters (RE: Proposal for Allow postgresql.conf values to be changed via
SQL [review])
|
Список | pgsql-hackers |
<p dir="ltr"><br /> On Jul 30, 2013 7:32 PM, "Josh Berkus" <<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br /> ><br /> ><br /> > I don't think you understoodGSmith's argument. For Debian/Ubuntu<br /> > sysadmins, configuration files live in /etc/, *period*. Evenones which<br /> > were automatically generated. The packagers and scripters of that OS<br /> > have taken asignificant amount of trouble to make that so, including<br /> > writing their own wrapper scripts around utilities forPostgres, Apache,<br /> > etc., in order to support putting all configuration files in /etc/.<br /> ><br /><p dir="ltr">Iused to be a Debian package maintainer. I packaged kerberos and afs and a number of smaller packages. I know whyDebian separates config files.<p dir="ltr">If a file is automatically maintained then it's internal program state justlike the list of users, databases, tables, etc.<p dir="ltr">Programs keep their state in /var. It would be just as wrongto put auto.conf in /etc as it is to put the existing postgresql.conf in PGDATA.
В списке pgsql-hackers по дате отправления: