Re: Parsing of pg_hba.conf and authentication inconsistencies - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Parsing of pg_hba.conf and authentication inconsistencies
Date
Msg-id 15237.1217737939@sss.pgh.pa.us
Whole thread Raw
In response to Re: Parsing of pg_hba.conf and authentication inconsistencies  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Parsing of pg_hba.conf and authentication inconsistencies  (Magnus Hagander <magnus@hagander.net>)
Re: Parsing of pg_hba.conf and authentication inconsistencies  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Robert Treat <xzilla@users.sourceforge.net> writes:
> Certainly there isn't any reason to allow a reload of a file that is just 
> going to break things when the first connection happens. For that matter,  
> why would we ever not want to parse it at HUP time rather than connect time? 

Two or three reasons why not were already mentioned upthread, but for
the stubborn, here's another one: are you volunteering to write the code
that backs out the config-file reload after the checks have determined
it was bad?  Given the amount of pain we suffered trying to make GUC do
something similar, any sane person would run screaming from the
prospect.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Parsing of pg_hba.conf and authentication inconsistencies
Next
From: Thomas Hallgren
Date:
Subject: Re: Re: [Pljava-dev] Should creating a new base type require superuser status?