Re: Explicit config patch 7.2B4
От | Peter Eisentraut |
---|---|
Тема | Re: Explicit config patch 7.2B4 |
Дата | |
Msg-id | Pine.LNX.4.30.0112161752370.641-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Explicit config patch 7.2B4 (mlw <markw@mohawksoft.com>) |
Ответы |
Re: Explicit config patch 7.2B4
|
Список | pgsql-hackers |
mlw writes: > This allows > > postmaster -C /etc/pgsql/mydb.conf > > The "-C" option specifies a configuration file. I'm still not happy about this, because given a pre-configured or already running system it is difficult or impossible to find out which configuration file is being used. This offsets in many ways the improved usability you're trying to achieve. I think an 'include' directive for postgresql.conf would solve this problem more generally (since it allows many more sharing models) and would also give us a good tool when we get to the configuration of alternative storage locations. Probably a command-line option could prove useful for testing purposes, etc., but I feel that by default the configuration should be written down in some easy-to-find file. This is consistent with the move away from command-line options that we have made with postgresql.conf. Probably we could make the option -C to mean "imagine an include directive written at the very start [or end?] of $PGDATA/postgresql.conf". With the default empty file this would achieve exactly the same thing as you're trying. Comments? -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: