> 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.
Can't do that. Postmaster has no database access. Must be fast.
--
Bruce Momjian
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
> >
> >
> >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 fo
>
>
>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 lookup
> We have the following item on TODO:
>
> * Overhaul pg_hba.conf host-based authentication
>
> Can people tell me what they want changed. I know we need the pg_shadow
> password field encrypted in the table and I will work on that now.
I haven't heard of any more issues with pg_hba.conf
