From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Willy-Bas Loos" <willybas(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Limit on number of users in postgresql? |
Date: | 2007-01-29 15:16:17 |
Message-ID: | 20070129101617.f58e571f.wmoran@collaborativefusion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Willy-Bas Loos" <willybas(at)gmail(dot)com> writes:
> > Tom Lane wrote:
> >> I think that the
> >> main bottleneck would be the "flat file" that's used to tell the
> >> postmaster about the set of valid users --- every time a user is
> >> added/dropped/changed, that file gets rewritten and then re-parsed
> >> by the postmaster. So you could eat a lot of overhead if you change
> >> users every few seconds or something like that.
>
> > What you describe Tom (flat file), sounds a bit strange to me. Aren't users
> > stored in a table? (pg_catalog.pg_authid)
>
> Yeah, but the postmaster can't read pg_authid, nor any other table,
> because it's not logically connected to the database. So any change
> to pg_authid gets copied to a "flat" ASCII-text file for the postmaster.
Would using kerberos or some other external auth mechanism work around this?
--
Bill Moran
Collaborative Fusion Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Randal L. Schwartz | 2007-01-29 15:38:31 | Re: Postgresql 8.1: plperl code works with LATIN1, fail |
Previous Message | Michael Fuhr | 2007-01-29 15:08:54 | Re: Postgresql 8.1: plperl code works with LATIN1, fail |