| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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 19:20:39 |
| Message-ID: | 20090808192039.GB9155@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
Tom Lane wrote:
> In some sense this is a bootstrap problem: what does it take to get to
> the point of being able to read pg_database and its indexes? That is
> necessarily not dependent on the particular database we want to join.
> Maybe we could solve it by having the relcache write a "global" cache
> file containing only entries for the global tables, and load that before
> we have identified the database we want to join (after which, we'll load
> another cache file for the local entries).
This sounds good, because autovacuum could probably use this too.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-08 19:25:27 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
| Previous Message | Tom Lane | 2009-08-08 19:15:39 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-08 19:25:27 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |
| Previous Message | Tom Lane | 2009-08-08 19:15:39 | Re: [PERFORM] BUG #4919: CREATE USER command slows down system performance |