| From: | "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br> |
|---|---|
| To: | <josh(at)agliodbs(dot)com> |
| Cc: | <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>, <scott(dot)marlowe(at)ihs(dot)com>, <nfesposi(at)sourceweave(dot)net>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: postgres eating CPU on HP9000 |
| Date: | 2004-03-29 10:57:43 |
| Message-ID: | 61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> Marcus,
>
>> We are experiencing exactly the same problem here, and we use 7.4 on
>> Linux/i386 SMP (2 processors). Our databases does even more access:
>> about 30k selects per hour, 10k updates and inserts per hour
>>
>> Vacuum analyze is done daily.
>
> What is your max_fsm_pages setting? If you are getting 10,000
> updates per hour, daily VACUUM ANALYZE may not be enough.
>
max_fsm_pages is set to 500000
> Also do you run VACUUM ANALYZE as a superuser, or as a regular user?
>
As a regular user (database owner). Is thery any difference when vacuuming
as a super user?
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
> joining column's datatypes do not match
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabio Esposito | 2004-03-29 13:09:22 | Re: postgres eating CPU on HP9000 |
| Previous Message | Andrew Rawnsley | 2004-03-28 19:49:54 | Re: column size too large, is this a bug? |