From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
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-07-15 15:10:30 |
Message-ID: | e51f66da0907150810i7a101247u9856ee72798849bf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
On 7/15/09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.
From security standpoint, wasting more cycles on bad passwords is good,
as it decreases the rate bruteforce password scanning can happen.
And I cannot imagine a scenario where performance on invalid logins
can be relevant..
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | David Wilson | 2009-07-15 15:16:23 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
Previous Message | Tom Lane | 2009-07-15 14:59:16 | Re: BUG #4919: CREATE USER command slows down system performance |
From | Date | Subject | |
---|---|---|---|
Next Message | David Wilson | 2009-07-15 15:16:23 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
Previous Message | Ibrahim Harrani | 2009-07-15 15:04:23 | Re: cluster index on a table |