From: Edoardo Ceccarelli <eddy@axa.it>
To: pgsql-performance@postgresql.org
Subject: slow seqscan
Date: Wed, 21 Apr 2004 09:17:23 +0200
Message-ID: <40862003.2090201@axa.it> (raw)
My first post to this list :)
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 (with certain filters) 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.
last friday morning, after that batch has been executed, the database
started responding really slowly to queries (expecially seq scans),
after a "vacuum full analize" things did get something better.
Yesterday the same: before the batch everything was perfect, after every
query was really slow, I've vacuum it again and now is ok.
Since now the db was working fine, it's 4 month's old with two updates
per week and I vacuum about once per month.
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
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: eddy@axa.it
Subject: Re: slow seqscan
In-Reply-To: <40862003.2090201@axa.it>
* 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