pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schaber <schabi@logix-tt.com>
To: kah_hang_ang@toray.com.my
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: extremely slow when execute select/delete for certain
Date: Mon, 08 May 2006 11:21:16 +0200
Message-ID: <445F0D8C.3040106@logix-tt.com> (raw)
In-Reply-To: <OFEE6DB213.EE330DAF-ON48257168.002AB1B5@pengroup.com.my>
References: <OFEE6DB213.EE330DAF-ON48257168.002AB1B5@pengroup.com.my>

Hi, Kah,

kah_hang_ang@toray.com.my wrote:

> I already vacuum those tables with full option but it still the same.
> 
> What could be the possible causes of this problem?
> How can I solve it?
> 
> CPU - Intel Xeon 2.40 GHz
> Memory - 1.5G
> Postgresql version: 7.2.2

First, you should consider to upgrade your PostgreSQL server to a newer
version, at least to 7.2.8 which fixes some critical bugs.

But it will be much better to upgrade to current 8.1 version, as I think
that your problem is caused by index bloat, and indices are handled much
better in 8.1.

Try recreating your indices using REINDEX command.

HTH,
Markus



-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org



view thread (4+ messages)  latest in thread

Message-ID: <445F0D8C.3040106@logix-tt.com>
Permalink:  ../445F0D8C.3040106@logix-tt.com/
Also on:    postgresql.org/message-id/445F0D8C.3040106@logix-tt.com

 · 

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: schabi@logix-tt.com, kah_hang_ang@toray.com.my
  Subject: Re: extremely slow when execute select/delete for certain
  In-Reply-To: <445F0D8C.3040106@logix-tt.com>

* 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