From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Rodrigo Moreno <rodrigo(dot)miguel(at)terra(dot)com(dot)br> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to improve postgres performace |
Date: | 2005-04-20 00:35:16 |
Message-ID: | 20050420003516.GW58835@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice pgsql-performance |
On Mon, Apr 18, 2005 at 11:36:01AM -0300, Rodrigo Moreno wrote:
> I really worried about that, because it's no enough anymore, and users claim
> about performace. But running the vacuumdb full, everthing starts to run
> better again, so i think the problem is not related to a specific query.
Vacuum full will skew your results, unless you plan on running vacuum
full all the time. This is because you will always have some amount of
dead tuples in a table that has any update or delete activity. A regular
vacuum doesn't remove these tuples, it just marks them as available. So
over time, depending on how frequently a table is vacuumed, it will
settle down to a steady-state size that is greater than it's size after
a vacuum full.
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | John DeSoi | 2005-04-20 05:05:58 | Re: Pqintaller for Windows Leaving me with Questions |
Previous Message | Bruno Depero | 2005-04-19 15:35:05 | problem migratin from ms sql |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-04-20 00:42:34 | Re: Sort and index |
Previous Message | Jim C. Nasby | 2005-04-20 00:30:54 | Re: immutable functions vs. join for lookups ? |