| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | stange(at)rentec(dot)com |
| Cc: | Vivek Khera <vivek(at)khera(dot)org>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: postgresql performance tuning |
| Date: | 2005-12-06 21:20:57 |
| Message-ID: | 16451.1133904057@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Alan Stange <stange(at)rentec(dot)com> writes:
> Vivek Khera wrote:
>> what evidence do you have that you are suffering index bloat?
> The files for the two indices on a single table used 7.8GB of space
> before a reindex, and 4.4GB after.
That's not bloat ... that's pretty nearly in line with the normal
expectation for a btree index, which is about 2/3rds fill factor.
If the compacted index were 10X smaller then I'd agree that you have
a bloat problem.
Periodic reindexing on this scale is not doing a lot for you except
thrashing your disks --- you're just giving space back to the OS that
will shortly be sucked up again by the same index.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-06 21:24:59 | Re: Missed index opportunity for outer join? |
| Previous Message | Ron Mayer | 2005-12-06 21:15:13 | Re: Missed index opportunity for outer join? |