| From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
|---|---|
| To: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
| Cc: | <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: LDAP lookup of connection parameters |
| Date: | 2006-04-18 07:22:52 |
| Message-ID: | 52EF20B2E3209443BC37736D00C3C13807F28E0F@EXADV1.host.magwien.gv.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> This patch for libpq allows you to enter an LDAP URL in
pg_service.conf.
> The URL will be queried and the resulting string(s) parsed for
> keyword = value connection options.
>
> The idea is to have connection information stored centrally on an LDAP
> server rather than on the client machine.
I forgot to mention that there was a brief discussion about this on
Hackers:
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00828.php
My implementation follows the idea from
http://archives.postgresql.org/pgsql-hackers/2006-02/msg01198.php
I thought it would be good to have some real code as a basis for
further discussion whether this is a desirable feature or not.
I felt somewhat encouraged because PostgreSQL already has a
dependency on OpenLDAP since
http://archives.postgresql.org/pgsql-patches/2005-12/msg00375.php
and I do not have to introduce a new dependency.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Brant | 2006-04-18 14:15:04 | Re: [Win32] Problem with rename() |
| Previous Message | Alvaro Herrera | 2006-04-18 03:45:24 | Re: Proposed doc-patch: Identifying the Current WAL file |