From: PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
To: pgsql-bugs@postgresql.org
Subject: BUG #1186: Broken Index?
Date: Fri, 2 Jul 2004 04:50:07 -0300 (ADT)
Message-ID: <20040702075007.B448FCF4D52@www.postgresql.com> (raw)
The following bug has been logged online:
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.
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: pgsql-bugs@postgresql.org
Subject: Re: BUG #1186: Broken Index?
In-Reply-To: <20040702075007.B448FCF4D52@www.postgresql.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