Re: BUG #15860: Postgresql service does not start when the pg_hba.conf is changed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabio Pardi <f(dot)pardi(at)portavita(dot)eu>
Cc: hiagorad(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15860: Postgresql service does not start when the pg_hba.conf is changed
Date: 2019-06-19 14:42:53
Message-ID: 6924.1560955373@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Fabio Pardi <f(dot)pardi(at)portavita(dot)eu> writes:
> On 19/06/2019 15:56, PG Bug reporting form wrote:
>> When I add a line on the file using the format "local all all
>> xx.xx.0.0/16 md5" the windows service does not start and gives on the
>> event viewer the error "Timed ou waiting for server startup".

> I think that is legit, since the correct format should be:
> local all all md5
> and no IP specified (else you should use 'host' instead of local)

Yeah. Also, the OP is on a Windows machine, and there's no point at
all in using "local" entries on Windows. Those apply to Unix-socket
connections, which is a concept Windows hasn't got. Instead use a
"host" line matching 127.0.0.1, and/or one for ::1 for IPV6.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Albrecht Scheidig 2019-06-19 15:47:59 XSS Bug in Query View
Previous Message Fabio Pardi 2019-06-19 14:10:25 Re: BUG #15860: Postgresql service does not start when the pg_hba.conf is changed