Re: Improving pg_hba.conf - Mailing list pgsql-hackers

From David Ford
Subject Re: Improving pg_hba.conf
Date
Msg-id 3B5BB843.50406@blue-labs.org
Whole thread Raw
In response to Re: Improving pg_hba.conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Improving pg_hba.conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
What I mean is, do host lookups first in the text file, then if a 
pg_hostaccess table (example) exists, check it for host entries.  This 
alleviates HUP or restart etc. to reload a config file.

David

Bruce Momjian wrote:

>>>
>>>I haven't heard of any more issues with pg_hba.conf so I will mark the
>>>item as done.  I did cleanup the comments in the file.  I have also
>>>added a TODO item:
>>>
>>>    * Read pg_hba.conf only on postmaster startup or SIGHUP
>>>
>>If you do this, can you add an access table for secondary lookups?  I 
>>tend to update host access frequently and personally I think it'd be 
>>dandy to have a table that can be updated for access as well as the 
>>primary pg_hba.conf file.
>>
>
>Sorry, I don't understand what secondary lookups are.
>




pgsql-hackers by date:

Previous
From: Grant
Date:
Subject: Large objects and table deletion.
Next
From: Bruce Momjian
Date:
Subject: Re: Improving pg_hba.conf