Re: postgres eating CPU on HP9000 - Mailing list pgsql-performance

From Marcus Andree S. Magalhaes
Subject Re: postgres eating CPU on HP9000
Date
Msg-id 61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br
Whole thread Raw
In response to Re: postgres eating CPU on HP9000  (Josh Berkus <josh@agliodbs.com>)
Responses Re: postgres eating CPU on HP9000  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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




pgsql-performance by date:

Previous
From: Andrew Rawnsley
Date:
Subject: Re: column size too large, is this a bug?
Next
From: Fabio Esposito
Date:
Subject: Re: postgres eating CPU on HP9000