pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #1186: Broken Index?
3+ messages / 3 participants
[nested] [flat]

* BUG #1186: Broken Index?
@ 2004-07-02 07:50 PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
  2004-07-02 13:12 ` Re: BUG #1186: Broken Index? Bruno Wolff III <bruno@wolff.to>
  2004-07-03 14:51 ` Re: BUG #1186: Broken Index? Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 2 replies; 3+ messages in thread

From: PostgreSQL Bugs List @ 2004-07-02 07:50 UTC (permalink / raw)
  To: pgsql-bugs@postgresql.org


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. 



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #1186: Broken Index?
  2004-07-02 07:50 BUG #1186: Broken Index? PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
@ 2004-07-02 13:12 ` Bruno Wolff III <bruno@wolff.to>
  1 sibling, 0 replies; 3+ messages in thread

From: Bruno Wolff III @ 2004-07-02 13:12 UTC (permalink / raw)
  To: Gosen, Hitoshi <mic-gosen@ns.inter-mic.co.jp>; +Cc: pgsql-bugs@postgresql.org; pgsql-performance

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.



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #1186: Broken Index?
  2004-07-02 07:50 BUG #1186: Broken Index? PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
@ 2004-07-03 14:51 ` Gaetano Mendola <mendola@bigfoot.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Gaetano Mendola @ 2004-07-03 14:51 UTC (permalink / raw)
  To: pgsql-bugs@postgresql.org

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






^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2004-07-03 14:51 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-07-02 07:50 BUG #1186: Broken Index? PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
2004-07-02 13:12 ` Bruno Wolff III <bruno@wolff.to>
2004-07-03 14:51 ` Gaetano Mendola <mendola@bigfoot.com>

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