From: patrick ~ <sidsrr@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: vacuum analyze slows sql query
Date: Wed, 3 Nov 2004 10:56:47 -0800 (PST)
Message-ID: <20041103185647.87443.qmail@web52105.mail.yahoo.com> (raw)
Greetings pgsql-performance :)
Yesterday I posted to the pgsql-sql list about an issue with VACUUM
while trying to track-down an issue with performance of a SQL SELECT
statement invovling a stored function. It was suggested that I bring
the discussion over to -performance.
Instread of reposting the message here is a link to the original
message followed by a brief summary:
http://marc.theaimsgroup.com/?l=postgresql-sql&m=109945118928530&w=2
Summary:
Our customer complains about web/php-based UI sluggishness accessing
the data in db. I created a "stripped down" version of the tables
in question to be able to post to the pgsql-sql list asking for hints
as to how I can improve the SQL query. While doing this I noticed
that if I 'createdb' and populate it with the "sanatized" data the
query in question is quite fast; 618 rows returned in 864.522 ms.
This was puzzling. Next I noticed that after a VACUUM the very same
query would slow down to a crawl; 618 rows returned in 1080688.921 ms).
This was reproduced on PostgreSQL 7.4.2 running on a Intel PIII 700Mhz,
512mb. This system is my /personal/ test system/sandbox. i.e., it
isn't being stressed by any other processes.
Thanks for reading,
--patrick
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
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: sidsrr@yahoo.com
Subject: Re: vacuum analyze slows sql query
In-Reply-To: <20041103185647.87443.qmail@web52105.mail.yahoo.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