Re: new feature: LDAP database name resolution
| От | Tom Lane |
|---|---|
| Тема | Re: new feature: LDAP database name resolution |
| Дата | |
| Msg-id | 15786.1141144673@sss.pgh.pa.us обсуждение |
| Ответ на | Re: new feature: LDAP database name resolution (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: new feature: LDAP database name resolution
|
| Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes:
> 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.
What other cases are actually interesting? How much code do we save
if we use libcurl instead of homegrown LDAP-accessing code? Does
libcurl bring in any secondary dependencies, or have limitations of
its own (thread safety is one obvious point to ask about)?
Depending on an outside library isn't free, so I think the tradeoff
has to be considered carefully.
regards, tom lane
В списке pgsql-hackers по дате отправления: