From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Wes <wespvp(at)syntegra(dot)com> |
Cc: | Postgresql-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Vacuum time degrading |
Date: | 2005-04-05 16:15:49 |
Message-ID: | 14267.1112717749@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Wes <wespvp(at)syntegra(dot)com> writes:
> On 4/4/05 8:50 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> That doesn't follow from what you said. Did you check that the physical
>> sizes of the indexes were comparable before and after the reindex?
> No, how do I do that (or where is it documented how to do it)?
The best way is probably to capture the output of VACUUM VERBOSE (not FULL)
for the table before and after REINDEX.
> How is it not consistent?
I didn't say it wasn't consistent, just that it doesn't prove the
point. The speedup you saw could have been from elimination of index
bloat more than from bringing the index into physically sorted order.
An estimate of the overall database size doesn't really tell us how
much this particular table's indexes changed in size.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Shraibman | 2005-04-05 16:24:02 | contrib/dbsize |
Previous Message | Tom Lane | 2005-04-05 16:11:44 | Re: Postmaster running out of discspace; Data corruption? |
From | Date | Subject | |
---|---|---|---|
Next Message | Wes | 2005-04-05 16:47:01 | Re: Vacuum time degrading |
Previous Message | Wes | 2005-04-05 16:08:25 | Re: Vacuum time degrading |