Bruce Momjian wrote:
mlw wrote:
I don't like the idea of specifying a directory, per se' because if you
have multiple database installations, how would you share the
configuration without symlinks?
Oh, for example, you would be sharing postgresql.conf, perhaps, but not
pg_hba.conf.
mlw wrote:
> I don't like the idea of specifying a directory, per se' because if you
> have multiple database installations, how would you share the
> configuration without symlinks?
Oh, for example, you would be sharing postgresql.conf, perhaps, but not
pg_hba.conf.
--
Bruce Momjian
Tom Lane wrote:
mlw <[EMAIL PROTECTED]> writes:
If no hba_conf and/or ident_conf setting is specified, the default
$PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
If you are trying to keep your config f
Tom Lane wrote:
> mlw <[EMAIL PROTECTED]> writes:
> > If no hba_conf and/or ident_conf setting is specified, the default
> > $PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
>
> Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
> If you are trying to keep your co
mlw <[EMAIL PROTECTED]> writes:
> If no hba_conf and/or ident_conf setting is specified, the default
> $PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
If you are trying to keep your config files out of the data d
This is a patch that allows PostgreSQL to use a configuration
file that is outside the main database directory.
It adds one more command line parameter, "-C" which
specifies the location of the postgres configuration file.
A patched version of PostgreSQL will function as:
postmaster -C /etc/post
