From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | olly(at)lfix(dot)co(dot)uk |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum (7.4) nss_ldap oddity |
Date: | 2004-09-01 15:24:21 |
Message-ID: | 4135E9A5.2030309@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Oliver Elphick wrote:
> I get this in the logs for every database open by pg_autovacuum:
>
> Sep 1 14:02:45 cerberus pg_autovacuum: nss_ldap: could not connect to
> any LDAP server as (null) - Can't contact LDAP server
>
> This is produced by the bind_to() call in libnss-ldap. This is invoked
> when /etc/nss_switch.conf specifies ldap; what I don't understand yet is
> what pg_autovacuum is doing differently from every other application so
> as to cause this message.
Good question, I don't know either. All pg_autovacuum does is call the
libpq function to connect to the database. Can you look into this
further? Do you get similar messages when you use psql to connect to a
database?
Matthew
From | Date | Subject | |
---|---|---|---|
Next Message | terry | 2004-09-01 15:27:29 | Re: PostgreSQL and Fedora? |
Previous Message | Russ Brown | 2004-09-01 15:20:58 | Re: Join efficiency |