From: | Jeff Boes <jboes(at)nexcerpt(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Vacuum stats interpreted? |
Date: | 2003-11-26 21:48:26 |
Message-ID: | d505c533699f41f775300967bfdf6b94@news.teranews.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
At some point in time, tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
>Jeff Boes <jboes(at)qtm(dot)net> writes:
>> The "Keep" and "UnUsed" numbers seem high to me, compared to other tables. Can
>> anyone interpret these and tell me anything about what we could do with this
>> table to make it "look" better?
>
>"Keep" is the number of rows that are committed dead but had to be kept
>anyway, because there are open transactions old enough to still
>potentially see them. The only way to reduce that is to not have old
>transactions hanging 'round while you vacuum.
>
>UnUsed is the number of empty line-pointer slots. At 4 bytes apiece,
>this would have to vastly exceed the number of live tuples before you
>should worry much.
For which values of "vastly"? I have a small table (1-2k rows) which has a ratio
of UnUsed:Tuples of 50-500.
The table in question has a ratio of about 10 or 11:1.
For some tables (not this one), we find that it significantly improves
performance (of non-indexed queries) to pg_dump and reload the table
periodically. I've been asked to try to quantify (from these vacuum numbers)
when we can predict that a dump-and-reload would be valuable.
From | Date | Subject | |
---|---|---|---|
Next Message | Michal Zaborowski | 2003-11-26 22:58:46 | Re: Size on Disk |
Previous Message | Tom Lane | 2003-11-26 21:43:37 | Re: Vacuum stats interpreted? |