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

From Bruce Momjian
Subject Re: Parsing of pg_hba.conf and authentication inconsistencies
Date
Msg-id 200808151802.m7FI2QV27452@momjian.us
Whole thread Raw
In response to Re: Parsing of pg_hba.conf and authentication inconsistencies  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Parsing of pg_hba.conf and authentication inconsistencies  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
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  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Automatic Client Failover
Next
From: Hannu Krosing
Date:
Subject: Re: proposal sql: labeled function params