From: | "Lauris Ulmanis" <lauris(dot)ulmanis(at)mykoob(dot)com> |
---|---|
To: | <pgsql-bugs(at)postgresql(dot)org> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Postgres user authentification or LDAP authentification |
Date: | 2009-07-23 10:47:47 |
Message-ID: | 4a683fe4.22a0100a.5945.7413@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
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? 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.
pgBouncer or pgPool uses Postgres users for connection pooling. Is there
some more variants to use connection pooling without using postgres users?
______________________________________
Lauris Ulmanis
Tel. +371 29471020
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Spies | 2009-07-23 12:56:36 | BUG #4935: Weird input syntax for intervals, part 2 |
Previous Message | Tom Lane | 2009-07-23 00:34:47 | Re: BUG #4934: regression in IN with joins in subselect |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-07-23 23:22:41 | Re: Performance difference between IN(...) and ANY(...) operator |
Previous Message | David Rees | 2009-07-22 19:29:25 | Re: Master/Slave, DB separation or just spend $$$? |