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

Re: Postgres user authentification or LDAP authentification

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Lauris Ulmanis <lauris(dot)ulmanis(at)mykoob(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres user authentification or LDAP authentification
Date: 2009-07-24 07:17:38
Message-ID: 9837222c0907240017k1809491bm79c461e80fb914fa@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-performance
On Thu, Jul 23, 2009 at 12:47, Lauris Ulmanis<lauris(dot)ulmanis(at)mykoob(dot)com> wrote:
> Hello!
>
>
>
> I posted you a message about slowness of creation users more than 500 000
> (#4919). It seems there is no workaround of this problem because of using
> pg_auth flat file.
>
>
>
> To override this problem is it possible to use LDAP authentification metod
> to identify each user and speed up system?

No. LDAP authentication still requires all the users to be created in
the database before they can log in. This is required so that they get
an oid in the system, that is used for all permissions checks and
ownership and such things.

The only thing you could do here is to map multiple users to the
*same* database user using pg_ident.conf, for example with a regular
expression. However, you then loose the ability to distinguish between
these users once they are logged in.


> How it will affect group roles
> for each user because we use groups roles to give Access to users to system
> objects? Because group roles will work only with postgres users not LDAP.

The PostgreSQL LDAP code currently has no support for groups.


> pgBouncer or pgPool uses Postgres users for connection pooling. Is there
> some more variants to use connection pooling without using postgres users?

Not that I know of.


-- 
 Magnus Hagander
 Self: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

pgsql-performance by date

Next:From: Robert HaasDate: 2009-07-26 03:31:55
Subject: Re: Very big insert/join performance problem (bacula)
Previous:From: Albe LaurenzDate: 2009-07-24 06:14:23
Subject: Re: Configuring Postgresql for writing BLOB at a high-rate

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2009-07-24 12:13:49
Subject: Re: BUG #4938: upgrade to 8.4 issue
Previous:From: Robert TreatDate: 2009-07-24 06:28:34
Subject: BUG #4940: Performance regression between 8.2 and 8.3.7

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