Mark Kirkwood wrote:Hmmm, the current setup handles this situation sensibly and without the need for symlinks. So this does not look like an improvement to me...
Bruce Momjian wrote:
My idea was to put config files in /usr/local/pgsql/data/etc, notSorry, I missed the 'data' pathname. However - I may be a bit slow - but I do not see how this will handle the situation where you have one installation of pgsql running several clusters. (I am not sure how common this situation is mind you)
pgsql/etc.
We don't put Unix configuration files in /, etc put them in /etc.
It is common. Moving things to data/etc will make things clearer, and
see my later email on an initdb option to put /data/etc/ somewhere else
and put a symlink for /data/etc.
This *could* work without symlinks if you introduce a "name" for each initialized cluster, and make this part of the config file name. This would mean that you could use 'data/etc' and have many config files therein, each of which would *unambiguously* point to a given cluster.
As a general point I share Tom's concern about breaking the association between the initialized cluster and its configuration file - e.g: I start "prod" with the configuration for "test" by mistake, and "test" has fsync=false... and something pulls the power...
regards
Mark
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
