From: | mlw <markw(at)mohawksoft(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | configuration files and PGDATA variable |
Date: | 2001-12-02 16:04:36 |
Message-ID: | 3C0A5114.F7DDB512@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I started to think about postgresql.conf.
Do you think it is a good idea, and how hard would it be, if postmaster and the
various utilities were able to read their whole setup from a postgresql.conf
file? Many UNIX utilities do this.
Think of this:
su pgsql -c "postmaster -C /etc/pgsql/mydb1.conf"
From this, postmaster can find all its settings in the config file. That way
you don't have to mess with startup scripts, environment variables, or anything
it just comes from the configuration file. Right now it is to hard to run two
different versions/instances of postgresql on the same machine.
Also, is there a real need to have a separate pg_hba.conf file? Couldn't
postgresql.conf also contain these settings?
I know this isn't of great concern to this group, but one of the things that
PostgreSQL does that kind of bugs me, is that it keeps its configuration and
data in the same place.
From | Date | Subject | |
---|---|---|---|
Next Message | James Thornton | 2001-12-02 18:31:48 | update returns 1, but no changes have been made |
Previous Message | mlw | 2001-12-02 15:45:13 | Re: Yet more logging questions |