pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marcus Andree S. Magalhaes <marcus.magalhaes@vlinfo.com.br>
To: josh@agliodbs.com
Cc: marcus.magalhaes@vlinfo.com.br
Cc: scott.marlowe@ihs.com
Cc: nfesposi@sourceweave.net
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres eating CPU on HP9000
Date: Mon, 29 Mar 2004 07:57:43 -0300 (BRT)
Message-ID: <61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br> (raw)
In-Reply-To: <200403281124.43275.josh@agliodbs.com>
References: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
	<Pine.LNX.4.33.0403261516420.8192-100000@css120.ihs.com>
	<62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br>
	<200403281124.43275.josh@agliodbs.com>

> 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






view thread (18+ messages)  latest in thread

Message-ID: <61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br>
Permalink:  ../61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br/
Also on:    postgresql.org/message-id/61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: marcus.magalhaes@vlinfo.com.br, josh@agliodbs.com, scott.marlowe@ihs.com, nfesposi@sourceweave.net
  Subject: Re: postgres eating CPU on HP9000
  In-Reply-To: <61715.200.174.148.100.1080557863.squirrel@webmail.webnow.com.br>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox