From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: new feature: LDAP database name resolution |
Date: | 2006-02-20 14:11:52 |
Message-ID: | 20060220141152.GO4474@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Martijn van Oosterhout (kleptog(at)svana(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2006-02-20 14:17:20 | Re: Feature Request |
Previous Message | Martijn van Oosterhout | 2006-02-20 14:02:54 | Re: new feature: LDAP database name resolution |