Magnus Hagander wrote: > > To address Magnus' specific question, right now we store the pg_hba.conf > > tokens as strings in the postmaster. I am fine with storing them in a > > more native format and throwing errors for values that don't convert. > > What would concern me is calling lots of 3rd party libraries from the > > postmaster to validate items. > > If I was unclear about that, that part was never part of what I > proposed. I'm only talking aobut parsing the syntax. The only external > calls in the code there now is the getaddrinfo calls to convert the IPs, > IIRC.
That seems safe to me. The use of strings for the pg_hba.conf content was only for convenience; I can see the advantage of using a more natural format. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
