Thread: BUG #15860: Postgresql service does not start when the pg_hba.conf is changed
BUG #15860: Postgresql service does not start when the pg_hba.conf is changed
From
PG Bug reporting form
Date:
The following bug has been logged on the website: Bug reference: 15860 Logged by: Hiago Diniz Email address: hiagorad@gmail.com PostgreSQL version: 9.6.13 Operating system: Windows Server 2008 Description: 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".
Re: BUG #15860: Postgresql service does not start when thepg_hba.conf is changed
From
Fabio Pardi
Date:
On 19/06/2019 15:56, PG Bug reporting form wrote: > The following bug has been logged on the website: > > 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) regards, fabio pardi
Re: BUG #15860: Postgresql service does not start when the pg_hba.conf is changed
From
Tom Lane
Date:
Fabio Pardi <f.pardi@portavita.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