From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Kelley <gkelley(at)britannicaviation(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Require Assistance Solving Problem - erroneous pg_hba.conf |
Date: | 2003-04-17 14:44:33 |
Message-ID: | 200304171444.h3HEiX316284@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> "Greg Kelley" <gkelley(at)britannicaviation(dot)com> writes:
> > pgsql log shows:
>
> > FATAL: Missing or erroneous pg_hba.conf file, see postmaster log for
> > details
> > "OG: parse_hba: invalid syntax in pg_hba.conf file at line 31, token "
>
> > Even the log entry doesn't look right - double quotes - and the .conf file
> > certainly doesn't have 31 lines!
>
> Indeed. I think it's a Windows-newline issue: you probably edited the
> config file with something that put in \r\n instead of \n. The
> overstruck LOG is a dead giveaway...
>
> I thought we had fixed the various config file parsers to be reasonably
> impervious to stray \r's, but you may have found a corner case where
> it's not recognized as whitespace. Try getting rid of the \r's.
Also, please don't wait a week and have your users frustrated before
asking for assistance --- we are here to help.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Murthy Kambhampaty | 2003-04-17 16:25:58 | Re: Require Assistance Solving Problem - erroneous pg_hba |
Previous Message | Tom Lane | 2003-04-17 14:40:55 | Re: Require Assistance Solving Problem - erroneous pg_hba.conf |