X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1EADBD1B51D for ; Sat, 3 Jul 2004 19:57:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17441-01 for ; Sat, 3 Jul 2004 22:57:37 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id F39F0D1B53E for ; Sat, 3 Jul 2004 19:57:34 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i63MvYi9019543 for ; Sat, 3 Jul 2004 22:57:35 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i63MmgvR017314 for pgsql-bugs@postgresql.org; Sat, 3 Jul 2004 22:48:42 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.bugs Subject: Re: BUG #1186: Broken Index? Date: Sat, 03 Jul 2004 16:51:50 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 37 Message-ID: References: <20040702075007.B448FCF4D52@www.postgresql.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en In-Reply-To: <20040702075007.B448FCF4D52@www.postgresql.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-bugs@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.6 tagged_above=0.0 required=5.0 tests=DATE_IN_PAST_06_12 X-Spam-Level: X-Archive-Number: 200407/44 X-Sequence-Number: 8626 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