From: | mlw <markw(at)mohawksoft(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Explicit config patch 7.2B4 |
Date: | 2001-12-16 14:35:58 |
Message-ID: | 3C1CB14E.5AEFF2F@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I guess I will maintain this for people who want it.
This allows
postmaster -C /etc/pgsql/mydb.conf
The "-C" option specifies a configuration file.
In the config file there are two more options:
datadir = '/u01/postgres'
hbaconfig = '/etc/pgsql/pg_hba.conf'
The "datadir" option specifies where the postgresql data directory resides. (My
original patch used the setting "pgdatadir" in which the "pg" seemed
redundant.)
The "hbaconfig" specifies where postgresql will look for the pg_hba.conf file.
If the "-D" option is specified on the command line, it overides the "datadir"
option in the config file. (This is a different behavior than my original
patch)
If No "datadir" is specified, it must be specified either on the command line
or the normal PGDATA environment variable.
If no "hbaconfig" setting is set, the it will look for pg_hba.config in the
data directory as always.
One can start many databases with the same settings as:
postmaster -C /path/default.conf -p 5432 -D /path/name1
postmaster -C /path/default.conf -p 5433 -D /path/name2
postmaster -C /path/default.conf -p 5434 -D /path/name3
Attachment | Content-Type | Size |
---|---|---|
explicit_config.patch.72b4 | text/plain | 6.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Doug McNaught | 2001-12-16 15:26:55 | Re: Explicit config patch 7.2B4 |
Previous Message | Jim Buttafuoco | 2001-12-16 14:12:14 | Re: Bulkloading using COPY - ignore duplicates? |