| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Cc: | Lamar Owen <lowen(at)pari(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_config, pg_service.conf, postgresql.conf .... |
| Date: | 2006-03-01 20:54:54 |
| Message-ID: | 200603012054.k21KssF29451@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Kirkwood wrote:
> > What if we add an option to initdb to allow the user to specify the name
> > and location of the postgresql.conf file?
>
> That is certainly a way to approach it, I see the tough bit being the
> parsing of postgresql.conf to figure out which parts of the global
> included file to ignore (i.e the stuff for the *other* clusters).
>
> Would this work for the situation where you have older clusters on the
> box (versions that don't understand 'include')?
>
> Additionally this would need to tackle start|stop etc for all clusters...
I guess I am thinking we should move in a direction where all the
postgresql.conf files can be put in a single directory and pg_ctl would
know how to process multiple config files, rather than create a central
file with conflicts with postgresql.conf.
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-01 20:55:21 | Re: [SQL] Interval subtracting |
| Previous Message | Mark Kirkwood | 2006-03-01 20:50:03 | Re: pg_config, pg_service.conf, postgresql.conf .... |