Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have PostgreSQL 8.4 configured to authenticate database users by performing a LDAP bind, as described in It works. However, for each login, it makes a new LDAP connection, sets up SSL, binds, and tears it down immediately afterwards. This is somewhat wasteful.

Is there any way of pooling these LDAP connections so that each database login only performs a bind, not an entire connection setup and teardown?

share|improve this question

I would suggest using PAM to authenticate, and configuring PAM to use LDAP? I think that the PAM LDAP auth module does the connection pooling you're referring to.

share|improve this answer
Hmm, maybe, except database users aren't system users. – Anonymoose May 12 '11 at 6:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.