From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Seum-Lim Gan <slgan(at)lucent(dot)com> |
Cc: | josh(at)agliodbs(dot)com, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: index file bloating still in 7.4 ? |
Date: | 2003-10-19 15:47:22 |
Message-ID: | 19692.1066578442@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Seum-Lim Gan <slgan(at)lucent(dot)com> writes:
> vacuum verbose analyze dsperf_rda_or_key;
> INFO: vacuuming "scncraft.dsperf_rda_or_key"
> INFO: index "dsperf242_1105" now contains 300000 row versions in 12387 pages
> DETAIL: 3097702 index row versions were removed.
> 0 index pages have been deleted, 0 are currently reusable.
Hm, interesting that you deleted 90% of the entries and still had no
empty index pages at all. What was the pattern of your deletes and/or
updates with respect to this index's key?
> However, when I check the disk space usage, it has not changed.
It won't in any case. Plain VACUUM is designed for maintaining a
steady-state level of free space in tables and indexes, not for
returning major amounts of space to the OS. For that you need
more-invasive operations like VACUUM FULL or REINDEX.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Seum-Lim Gan | 2003-10-19 16:55:57 | Re: index file bloating still in 7.4 ? |
Previous Message | Seum-Lim Gan | 2003-10-19 14:46:08 | Re: index file bloating still in 7.4 ? |