Re: new feature: LDAP database name resolution - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: new feature: LDAP database name resolution
Date
Msg-id 20060220141152.GO4474@ns.snowman.net
Whole thread Raw
In response to Re: new feature: LDAP database name resolution  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: new feature: LDAP database name resolution
List pgsql-hackers
* Martijn van Oosterhout (kleptog@svana.org) wrote:
> Perhaps you should look into pg_service.conf. It's a configuration file
> such that in your connect line you can say:
>
> PQconnect("service=production");
>
> and in the config file you say:
>
> [production]
> host=db1
> port=5434
> dbname=main
>
> It's not quite as nice as LDAP to be sure, but it might work well
> enough for your config. For example, you could write a program to
> generate that file from an LDAP database.

If LDAP is really what you're after, though, it seems to me one approach
that would involve changing only libpq (I think...) would be to support
having the 'pg_service.conf' in LDAP, essentially.  Perhaps with a
seperate namespace (ie: "service=ldap:production"), or maybe as a
fall-back if the name isn't found in a local pg_service.conf.

Just some thoughts,
Stephen

pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: new feature: LDAP database name resolution
Next
From: "Jonah H. Harris"
Date:
Subject: Re: Feature Request