Rapid deteriation of performance (might be caused by tsearch?) in 7.3.2 - Mailing list pgsql-bugs

From Robert John Shepherd
Subject Rapid deteriation of performance (might be caused by tsearch?) in 7.3.2
Date
Msg-id 000201c2fa97$dc2197f0$f3b0313e@LAIKA
Whole thread Raw
Responses Re: Rapid deteriation of performance (might be caused by tsearch?) in 7.3.2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Up until a few days ago I have been running Postgresl 7.2.3 with Tsearch
from the contrib dir, but at various times the performance of the
database would suddenly and rapidly deteriate so that queries which
previously took 500ms then took 8 or 9 seconds.

The only cure is a backup and restore of the database, vacuuming and
analysing does nothing. I even tried rebuilding all indexes once which
didn't seem to help.

This was an annoying but intermittent thing, which happened the last
time this Wednesday. Since I was doing a backup and restore anyway, I
decided to upgrade to 7.3.2 in the hope this might fix the annoying
problem, however it has made it WAY worse.

Rather than going a few weeks (and sometimes months) in between having
to use this fix, I am now having to do it almost every single day. I'm
now lucky if it lasts 24 hours before it brings my website to a total
crawl.

There is nothing special about my database other than the fact that I
use the Tsearch addon. Now if I go and do a bit update to the Tsearch
indexes on a table, with for example:

    UPDATE tblmessages SET strmessageidx=txt2txtidx(strheading || '
' || strmessage);

Then that instantly brings the whole database to a crawl, which no
amount of index rebuilding, vacuuming and analysing helps.

Help! (And sorry if this is the wrong list)



Yours Unwhettedly,
Robert John Shepherd.

Editor
DVD REVIEWER
The UK's BIGGEST Online DVD Magazine
http://www.dvd.reviewer.co.uk

For a copy of my Public PGP key, email: pgp@robertsworld.org.uk

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #933: Too many inserts crash server
Next
From: "lists"
Date:
Subject: index problem when renaming a table