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

From Tom Lane
Subject Re: new feature: LDAP database name resolution
Date
Msg-id 15786.1141144673@sss.pgh.pa.us
Whole thread Raw
In response to Re: new feature: LDAP database name resolution  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: new feature: LDAP database name resolution  (Andrew Dunstan <andrew@dunslane.net>)
List 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 by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Vacuum dead tuples that are "between" transactions
Next
From: "Jim C. Nasby"
Date:
Subject: Re: temporary indexes