pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: pgsql-bugs@postgresql.org
Subject: Re: BUG #1186: Broken Index?
Date: Sat, 03 Jul 2004 16:51:50 +0200
Message-ID: <cc6h6h$fnu$1@floppy.pyrenet.fr> (raw)
In-Reply-To: <20040702075007.B448FCF4D52@www.postgresql.com>
References: <20040702075007.B448FCF4D52@www.postgresql.com>

PostgreSQL Bugs List wrote:
> 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. 

This is not for sure a bug, but a known behaviour if you don't vacuum at all
your db. I bet you don't use the vacuum daemon; use it or schedule a simple
vacuum on the eavily updated table each 10 minutes. I strongly suggest you to use
the autovacuum daemon.

Do not esitate to ask how use it.


Regards
Gaetano Mendola






view thread (3+ messages)

Message-ID: <cc6h6h$fnu$1@floppy.pyrenet.fr>
Permalink:  ../cc6h6h$fnu$1@floppy.pyrenet.fr/
Also on:    postgresql.org/message-id/cc6h6h$fnu$1@floppy.pyrenet.fr

 · 

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: mendola@bigfoot.com, pgsql-bugs@postgresql.org
  Subject: Re: BUG #1186: Broken Index?
  In-Reply-To: <cc6h6h$fnu$1@floppy.pyrenet.fr>

* 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