> Just guessing from the function name, but does this go away if you > don't configure --with-ldap? > > If so it's presumably a portability issue in this recent patch: > > 2006-03-06 12:41 momjian > > * configure, configure.in, src/backend/libpq/auth.c, > src/backend/libpq/hba.c, > src/backend/libpq/pg_hba.conf.sample, > src/include/pg_config.h.in, src/include/libpq/hba.h: This > patch > adds native LDAP auth, for those platforms that don't have > PAM > (such as Win32, but also unixen without PAM). On Unix, uses > OpenLDAP. On win32, uses the builin WinLDAP library. > > Magnus Hagander > > I'd counsel just leaving --with-ldap off until Magnus gets back > from vacation. We can always revert the patch later if he can't > fix it. > (There's some fairly ugly stuff going on at lines 69-89 of > backend/libpq/auth.c, which I bet is the root of the trouble, but > I'm not going to dig further --- I've wasted more than enough time > on Windows this week ;-))
Looking at the MSDN documentation it seems this function only exists on Windows 2003 and Windows XP. Which is very interesting, because I have it working on one of my 2000 boxes. But I guess I got it through some patch or other. I'm going to have to redo it to dynamically load that function and exit with a proper error message if it's not found. Shouldn't be too hard, I'll get to it as soon as I can get down for a coding session. The ugly stuff I assume is the stuff about the mingw broken headers? If so, no, not related in any way. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
