pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Gosen, Hitoshi <mic-gosen@ns.inter-mic.co.jp>
Cc: pgsql-bugs@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: BUG #1186: Broken Index?
Date: Fri, 2 Jul 2004 08:12:58 -0500
Message-ID: <20040702131258.GB25007@wolff.to> (raw)
In-Reply-To: <20040702075007.B448FCF4D52@www.postgresql.com>
References: <20040702075007.B448FCF4D52@www.postgresql.com>

On Fri, Jul 02, 2004 at 04:50:07 -0300,
  PostgreSQL Bugs List <pgsql-bugs@postgresql.org> wrote:
> 
> The following bug has been logged online:

This doesn't appear to be a bug at this point. It sounds like you have
a self induced performance problem, so I am moving the discussion to
pgsql-performance.

> 
> Bug reference:      1186
> Logged by:          Gosen, Hitoshi
> 
> Email address:      mic-gosen@ns.inter-mic.co.jp
> 
> PostgreSQL version: 7.4
> 
> Operating system:   linux 2.4.18
> 
> Description:        Broken Index?
> 
> Details: 
> 
> Hello All,
> We are using PostgreSQL 7.4.2 for our website that handles over 200,000 
> transactions a day. 
> About a month ago, the responses from the SELECT queries on the database 
> became terribly slow. 
> We tried to anaylze the cause of the problem, searching throught the system 
> logs and all, but nothing appeared to be out of the ordinary. 
> 
> What we did to resolve this was to dump the database, delete the database, 
> recreate the database, and finally restore it. After that, things were back 
> to normal. 
> 
> From the above experience, we were able to hypothesize that the fault of the 
> slow responses was not from a broken data or hardware failures, but from a 
> broken index, since we were able to recover 100% of the data on the same 
> machine. 
> 
> Today, the same problem occured, and the same actions are going to be taken 
> to temporary resolve it. 
> 
> Final note: we will also experiment with the  'vacuum full' command to see 
> if it counters this problem. 

It sounds like you aren't properly vacuuming your database. It is possible
that you need a higher FSM setting or to vacuum more frequently.



view thread (3+ messages)  latest in thread

Message-ID: <20040702131258.GB25007@wolff.to>
Permalink:  ../20040702131258.GB25007@wolff.to/
Also on:    postgresql.org/message-id/20040702131258.GB25007@wolff.to

 · 

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: bruno@wolff.to, mic-gosen@ns.inter-mic.co.jp, pgsql-bugs@postgresql.org
  Subject: Re: BUG #1186: Broken Index?
  In-Reply-To: <20040702131258.GB25007@wolff.to>

* 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