| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Date: | 2008-08-15 18:02:26 |
| Message-ID: | 200808151802.m7FI2QV27452@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2008-08-15 18:20:47 | Re: proposal sql: labeled function params |
| Previous Message | Simon Riggs | 2008-08-15 17:44:21 | Re: Automatic Client Failover |