How about it becomes part of 'pg_ctl status'? At the moment it doesn't seem to provide much information given that
peopleset most parameters in the conf file(s). It would be nice to see more than just the PID and the commandline
paramsthere (eg I don't have any :-). Perhaps its off topic for pg_hba.conf but it would be nice for postgresql.conf
info.
My 2 cents.
cheers,
thalis
On Thu, 14 Jun 2001, Tom Lane wrote:
> Frank Miles <fpm@u.washington.edu> writes:
> > Mystery solved. As originally expected, something *stupid*. It turns
> > out that postgres was reading the pg_hba.conf in /opt/pgsql/data/; I
> > was editing (and expecting postgres to read) the file in /etc/postgresql.
>
> Ouch. Now that I think about it, you're not the first person to make
> this type of error. Seems like it might be a good idea if at
> sufficiently high -d levels, the postmaster would spit out to its log
> every line read from the config file(s). That would give some way of
> detecting that the Wrong Thing is happening. Comments? Does anyone
> have a better idea?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
