Re: new feature: LDAP database name resolution

>>I have added a configure option --with-openldap to enable the code.
>>
>>Does that make sense to you?
>>
>>Should I try to polish and test the code and submit it as a patch
>
> I would still much prefer to see remote config fetching done in a more

> general way, using say libcurl (which handles ldap just fine if
openldap
> is available). Then we could fetch the config from a variety of
sources,
> not just ldap. Libcurl uses a modified MIT license, so we should not
> have any problems on that score. And with luck it would involve less
> postgres code maintenance.

So if I make the effort to modify the LDAP support to curl support,
would the community be interested?

Since we here use only LDAP, I would only want to embark on this if
you want to add it to PostgreSQL (if my code is good enough,
of course).

Yours,
Laurenz Albe