From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, toruvinn <toruvinn(at)lain(dot)pl>, pgsql-bugs(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
Date: | 2009-08-08 04:13:49 |
Message-ID: | 200908080413.n784Dn913949@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > toruvinn wrote:
> >> I was always wondering, though, why PostgreSQL uses this approach and not
> >> its catalogs.
>
> > It does use the catalog for most things. THe flatfile is used for the
> > situations where the catalogs are not yet ready to be read.
>
> Now that we have SQL-level CONNECT privilege, I wonder just how much
> functionality would be lost if we got rid of the flat files and told
> people they had to use CONNECT to do any per-user or per-database
> access control.
>
> The main point I can see offhand is that password checking would have
> to be done a lot later in the startup sequence, with correspondingly
> more cycles wasted to reject bad passwords.
Is this a TODO?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-08 16:02:06 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
Previous Message | psqluser | 2009-08-07 11:50:55 | Connections closed unexpectedly |
From | Date | Subject | |
---|---|---|---|
Next Message | Fizu | 2009-08-08 06:02:47 | ORDER BY ... LIMIT and JOIN |
Previous Message | Robert Haas | 2009-08-08 03:37:35 | Re: SQL select query becomes slow when using limit (with no offset) |