From: Ian FREISLICH <if@hetzner.co.za>
To: pgsql-admin@postgresql.org
Cc: Steve <steve@hotmail.com>
Subject: Re: please please please PLEASE help!
Date: Fri, 30 Jul 2004 14:59:01 +0200
Message-ID: <E1BqWyT-000Oqe-00@hetzner.co.za> (raw)
In-Reply-To: <rbamber@openworld.org> <NJEBKAGMPKNPDHGFFJJDKEJLCHAA.rbamber@openworld.org>
"Rob Bamber" wrote:
> Another thought -
>
> We had a similar issue recently. Our support guys dropped the
> database and then rebuilt it from a dump file. The size of the data
> directory went down from 12GB to less than 2GB. According to the sys
> ad that did the work postgres is not very good a reclaiming disk space
> after large quantities of tuples are deleted over time.
And another thought,
Have you tried clustering your tables on the most frequently used
and/or time-important index in your joins? (remember to VACUUM
ANALYZE after the cluster has completed) You might find a huge
performance increase. Clustering should also fix the problem
mentioned above because the table is physically re-written on disk.
Use EXPLAIN ANALYZE to find out which is the most time-consuming
part of your query and optimise that.
Also, have you analyzed your database recently? If you've never
run VACUUM ANALYZE your query planner's statistics have never been
updated so the query planner might not be making the best choices.
Ian
--
Ian Freislich
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: if@hetzner.co.za, steve@hotmail.com
Subject: Re: please please please PLEASE help!
In-Reply-To: <E1BqWyT-000Oqe-00@hetzner.co.za>
References: <E1BqWyT-000Oqe-00@hetzner.co.za>
* 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