On Wed, Feb 22, 2006 at 09:22:14AM -0500, Mark Woodward wrote:
> That's not the issue.
> I find it frustrating sometimes because when I describe one scenario,
> people debate it using other scenarios. Maybe I lack the communications
> skills to convey the problem accurately.
<snip>
> Now, if there were a standard file from which you could "see" what
> databases are installed and running on this system, you could write a
> shell script:
If you're talking about standards perhaps you should consider how
Debian does it. All configuration is stored in
/etc/postgresql/<version>/<clustername>/
It provides wrapper scripts to run pg_ctl (pg_ctlcluster) on any
particular cluster which can be run by either the system user owning
the db, or root.
Within those files is all the information required to find the cluster
(base directory, etc).
I think the default config is to start all clusters on bootup. The main
downside of this system is that some sysadmin pretty much needs to
create the clusters for everyone. Kinda logical given the location of
the configuration.
I doubt something like this would ever make it into the standard
distribution though. What you're asking is more a distributer issue
than an issue for postgres.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.