On Thu, 13 Feb 2003, mlw wrote: > > > Robert Treat wrote: > > >On Thu, 2003-02-13 at 09:23, mlw wrote: > > > > > >>I deal with a number of PG databases on a number of sites, and it is a > >>real pain in the ass to get to a PG box and hunt around for data > >>directory so as to be able to administer the system. What's really > >>annoying is when you have to find the data directory when someone else > >>set up the system.
You realize that the actual code feature doesn't necessarily help this case, right? Putting configuration in /etc and having a configuration file option on the command line are separate concepts. I think the feature is worthwhile, but I have some initial condition functionality questions that may have been answered in the previous patch, but I don't remember at this point. Mostly these have to deal with initial creation. Does the user specify an output location to initdb, do they just specify a data dir as now where the configuration goes but then they need to move it somewhere, does initdb now do nothing relating to configuration file and the user should make one on his own. Related, is the admin expected to have already made (say) /etc/postgresql to stick the config in and set the permissions correctly (since initdb doesn't run as root)? ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
