Skip site navigation (1) Skip section navigation (2)

Re: new feature: LDAP database name resolution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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-28 16:37:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)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

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-02-28 16:40:27
Subject: Re: [HACKERS] how solve diff of API counstruct_md_array between
Previous:From: Jim C. NasbyDate: 2006-02-28 16:28:59
Subject: Re: Vacuum dead tuples that are "between" transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group