From: Frank Wiles <frank@wiles.org>
To: Ron St-Pierre <rstpierre@syscor.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Table UPDATE is too slow
Date: Tue, 31 Aug 2004 13:46:19 -0500
Message-ID: <20040831134619.4ead03b0.frank@wiles.org> (raw)
In-Reply-To: <4134BF36.3000504@syscor.com>
References: <4134BF36.3000504@syscor.com>
On Tue, 31 Aug 2004 11:11:02 -0700
Ron St-Pierre <rstpierre@syscor.com> wrote:
> Postgres 7.4.3
> debian stable
> 2 GB RAM
> 80 DB IDE drive (we can't change it)
>
> shared_buffers = 2048
> sort_mem = 1024
> max_fsm_pages = 40000
> checkpoint_segments = 5
> random_page_cost = 3
I agree with all of the follow ups that having indexes on every
column is a bad idea. I would remove the indexes from the
least searched upon 10-20 columns, as I'm sure this will help
your performance.
You mention that not having indexes on some of the columns because it
"may slow down user queries". I think you should investigate this and
make sure they are necessary. I've seen many an application, with far
more rows than you're dealing with, only need 1 or 2 indexes, even
when all (or most) columns could be searched.
Also, you should consider increasing your shared_buffers and probably
your sort memory a touch as well. This will help your overall
performance.
---------------------------------
Frank Wiles <frank@wiles.org>
http://www.wiles.org
---------------------------------
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: frank@wiles.org, rstpierre@syscor.com
Subject: Re: Table UPDATE is too slow
In-Reply-To: <20040831134619.4ead03b0.frank@wiles.org>
* 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