From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Sahagian, David" <david(dot)sahagian(at)emc(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: FATAL logged when starting |
Date: | 2013-02-21 16:41:30 |
Message-ID: | 27937.1361464890@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Sahagian, David" <david(dot)sahagian(at)emc(dot)com> writes:
> We get this FATAL pg_log entry, just after Postgres startup.
> FATAL: no pg_hba.conf entry for host "[local]", user "rsaadmin", database "postgres", SSL off
> Postgres is run under the linux user account "rsaadmin", but we don't have a Postgres role by that name.
> Is there a way for me to specify a DIFFERENT USER, that pg_ctl will use to determine postgres has started ?
I think you could set PGUSER in pg_ctl's environment.
> If not, how do people work around getting this nasty FATAL log message ?
You could just ignore it ... it's harmless.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | François Beausoleil | 2013-02-21 16:52:35 | Determining last auto vacuum / analyze |
Previous Message | Sahagian, David | 2013-02-21 16:34:55 | FATAL logged when starting |