Hi,

After switching to LDAP authentication on our system, I noticed that
PostgreSQL start-up (and shut-down) time because ridiculously high.
(The PostgreSQL server isn't used as the back-end for LDAP; the LDAP
servers sits elsewhere).

Searching through google yielded the following post which seems still
unresolved:
http://www.mail-archive.com/debian-u...msg483707.html

By looking at the LDAP server logs, I noticed that during the long time
it takes the PostgreSQL server to start, it continuously queries the
LDAP server (there are many hundreds of users and groups in our domain).

Looking back at the start-up code, I narrowed the program down to the
/usr/share/postgresql-common/PgCommon.pm file, and more specifically
the function "change_ugid()": this functions loops through the entire
LDAP database, entry by entry, repeatedly querying the LDAP server and
consuming cpu, network and most of all lost of time ...

This seems like a bug (inefficient implementation) in PostgreSQL.
(it doesn't look like a problem in the way the LDAP client side - or
server - have been setup).

This problem is verified for postgresql-client-common versions 8.1,
and 8.3 on debian unstable, and testing.

I'd appreciate suggestions as how this can be solved.

Thanks,

Oren.

(ps. please CC me as I'm not subscribed to the list)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Jan 29, 2008 at 03:01:27AM -0500, Oren Laadan wrote:
> Hi,
>
> After switching to LDAP authentication on our system, I noticed that
> PostgreSQL start-up (and shut-down) time because ridiculously high.
> (The PostgreSQL server isn't used as the back-end for LDAP; the LDAP
> servers sits elsewhere).
>
> Searching through google yielded the following post which seems still
> unresolved:
> http://www.mail-archive.com/debian-u...msg483707.html
>
> By looking at the LDAP server logs, I noticed that during the long time
> it takes the PostgreSQL server to start, it continuously queries the
> LDAP server (there are many hundreds of users and groups in our domain).
>
> Looking back at the start-up code, I narrowed the program down to the
> /usr/share/postgresql-common/PgCommon.pm file, and more specifically
> the function "change_ugid()": this functions loops through the entire
> LDAP database, entry by entry, repeatedly querying the LDAP server and
> consuming cpu, network and most of all lost of time ...
>
> This seems like a bug (inefficient implementation) in PostgreSQL.
> (it doesn't look like a problem in the way the LDAP client side - or
> server - have been setup).
>
> This problem is verified for postgresql-client-common versions 8.1,
> and 8.3 on debian unstable, and testing.
>
> I'd appreciate suggestions as how this can be solved.
have you tried using nscd ?

>
> Thanks,
>
> Oren.
>
> (ps. please CC me as I'm not subscribed to the list)
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

--
"And so, in my State of the -- my State of the Union -- or state -- my speech to the nation, whatever you want to call it, speech to the nation -- I asked Americans to give 4,000 years -- 4,000 hours over the next -- the restof your life -- of service to America."

- George W. Bush
04/09/2002
Bridgeport, Conn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHnwtZkZz88chpJ2MRAmOqAJ9/WTeONuqEf+uY7XUlu76M6IaOQwCfZEut
V4M5ySV7E8jSz5uci4nio9M=
=Y3os
-----END PGP SIGNATURE-----