Parsing errors in pg_hba.conf - Mailing list pgsql-hackers

From Magnus Hagander
Subject Parsing errors in pg_hba.conf
Date
Msg-id 4905A528.7070501@hagander.net
Whole thread Raw
Responses Re: Parsing errors in pg_hba.conf
Re: Parsing errors in pg_hba.conf
List pgsql-hackers
In a number of places in pg_hba.conf, we don't actually log what goes
wrong - instead we just goto a label that will log "invalid token \"%s\"".

Is there any special reason for this, other than the fact that it was
the easy way out? I think it would be reasonable to for example log
"hostssl not supported on this platform" instead of that, when USE_SSL
is not defined, etc.

//Magnus


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: crypt auth
Next
From: Tom Lane
Date:
Subject: Re: WIP patch: convert SQL-language functions to return tuplestores