X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 03986D1D085 for ; Fri, 16 Apr 2004 20:18:39 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 23184-06 for ; Fri, 16 Apr 2004 20:18:35 -0300 (ADT) Received: from smtp3.aruba.it (smtp3.aruba.it [62.149.128.202]) by svr1.postgresql.org (Postfix) with SMTP id D4A8CD1D062 for ; Fri, 16 Apr 2004 20:18:35 -0300 (ADT) Received: (qmail 30137 invoked from network); 16 Apr 2004 23:18:37 -0000 Received: from unknown (HELO axa.it) (80.183.237.64) by smtp3.aruba.it with SMTP; 16 Apr 2004 23:18:36 -0000 Message-ID: <408069D2.4040206@axa.it> Date: Sat, 17 Apr 2004 01:18:42 +0200 From: Edoardo Ceccarelli User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: it, en, en-us MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: slow seqscan Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: smtp3.aruba.it 1.6.2 0/1000/N X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/237 X-Sequence-Number: 13210 I have already posted a similar topic months ago, that time I had a strange behaviour checking response time of seqscan after a vacuum, but now has happened again in another situation. Scenario: I have a database used only with search queries with only one table that holds about 450.000/500.000 records. The table is well indexed so that most of the queries are executed with index scan but since there is a big text field in the table (360chars) some search operation ends up with seq scans. This table is not written during normal operation: twice per week there is a batch program that insert about 35.000 records and updates another 40.000. this morning, after that batch has been executed, the database started responding really slowly to seq scan queries, also after a "vacuum full analize" things didn't get better. I am using version 7.3 do I need to upgrade to 7.4? also, I was thinking about setting this table in a kind of "read-only" mode to improve performance, is this possible? Thank you for your help Edoardo Ceccarelli