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?
As the one just bitten, it sounds great to me. Filenames (including full
path) and relevant environment variable values would be great, too.
-frank
