From: | Olivier Jeannet <olivier(dot)jeannet(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5329: postmaster fails to start because of an erroneous pg_hba.conf, but doesn't output any error |
Date: | 2010-02-17 08:37:26 |
Message-ID: | bbcf0b041002170037k565fa56ds3c66400e0fb874f1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Feb 17, 2010 at 2:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We most certainly do print something --- in your example I get this:
>
> LOG: invalid authentication method "127.0.0.1"
> CONTEXT: line 81 of configuration file "/home/postgres/data/pg_hba.conf"
> FATAL: could not load pg_hba.conf
>
> I suspect you are using a configuration that redirects the postmaster's
> log to /dev/null, or some equally unhelpful place :-(.
>
> FWIW, this message comes out after the logging settings in
> postgresql.conf have been adopted, so you should look to those to see
> where the message actually went. Errors in postgresql.conf itself
> typically get reported on postmaster's stderr.
You are right, I wasn't looking at the right place (I was a user of
Postgres a very long time ago).
Sorry for this unnecessary bug report, and thanks to you and to Euler
who answered as well.
Best regards,
Olivier Jeannet.
From | Date | Subject | |
---|---|---|---|
Next Message | Takahiro Itagaki | 2010-02-17 08:43:19 | Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
Previous Message | zhuge | 2010-02-17 05:41:45 | BUG #5330: No CREATE SYNONYM command |