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

Re: BUG #4919: CREATE USER command slows down system performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: toruvinn <toruvinn(at)lain(dot)pl>, pgsql-bugs(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: BUG #4919: CREATE USER command slows down system performance
Date: 2009-07-15 14:59:16
Message-ID: 22612.1247669956@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-performance
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.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Ibrahim HarraniDate: 2009-07-15 15:04:23
Subject: Re: cluster index on a table
Previous:From: Alvaro HerreraDate: 2009-07-15 14:47:35
Subject: Re: BUG #4919: CREATE USER command slows down systemperformance

pgsql-bugs by date

Next:From: Marko KreenDate: 2009-07-15 15:10:30
Subject: Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance
Previous:From: Alvaro HerreraDate: 2009-07-15 14:47:35
Subject: Re: BUG #4919: CREATE USER command slows down systemperformance

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