From: | mlw <pgsql(at)mohawksoft(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: location of the configuration files |
Date: | 2003-02-13 15:19:11 |
Message-ID: | 3E4BB76F.8040504@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>mlw <pgsql(at)mohawksoft(dot)com> writes:
>
>
>>Here is the test, configure a server, with sendmail, named, apache, and
>>PostgreSQL. Tell me which of these systems doesn't configure right.
>>
>>
>
>AFAIK, only one of those four is designed to support multiple instances
>running on a single machine. This is not unrelated.
>
>
>
While I will agree with you on sendmail and named, Apache is often run
more than once with different options.
Furthermore, I hate to keep bringing it up, Oracle does use the
configuration file methodology.
Tom, I just don't understand why this is being resisted so vigorously.
What is wrong with starting PostgreSQL as:
postmaster -C /etc/postgresql.conf
UNIX admins would love to have this as a methodology, I don't think you
can deny this, can you? I, as a long term PG user, really really want
this, because in the long run, it makes PostgreSQL easier to administer.
If a patch allows PG to function as it does, but also allows a
configuration file methodology, why not?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-13 15:20:20 | Re: set_ps_display on solaris x86 |
Previous Message | Tom Lane | 2003-02-13 15:06:29 | Re: [HACKERS] Changing the default configuration (was Re: |