Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> AFAICS, you can either set -C to /etc if you want your PG config files
>> loose in /etc, or you can set it to /etc/postgresql/ if you want them
>> in a privately-owned directory. Which other arrangements are needed?
> People might want to share them between servers, or allow a user to select
> from a few pre-configured ones that which reside in the same directory.
You can accomplish that without the need to customize the .conf file
names; you just make, eg,
/etc/postgres/myconfig/postgresql.conf
/etc/postgres/yourconfig/postgresql.conf
/etc/postgres/herconfig/postgresql.conf
(plus additional config files as needed in each of these directories)
and then the postmaster start command is
postmaster -C /etc/postgres/myconfig
I see no real gain in flexibility in allowing people to choose random
names for the individual config files. Also, it'd defeat the
ultimate-fallback approach of doing "find / -name postgresql.conf"
to figure out where the config files are hiding in an unfamiliar
installation.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
