From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
---|---|
To: | "C(dot) Bensend" <benny(at)bennyvision(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: VARCHAR -vs- CHAR: huge performance difference? |
Date: | 2004-06-16 04:56:11 |
Message-ID: | 009601c4535e$3e8d10c0$7201a8c0@mst1x5r347kymb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> Or do I just need to vacuum more often? I _did_ try a vacuum before
> asking the list for help, but it didn't give any improvement (just a
> vacuum analyze).
"vacuum analyse" allows dead space to be re-used, but doesn't compact the
table, you need "vacuum analyse full" for that.
I'm not sure how the free space map relates to this, maybe someone can shed
some light, but if it is too small, not all dead rows can be re-used (as I
understand it). If your table (or even the DB in general) is updated alot,
the default FSM size that comes with 7.3 may not be enough to ensure the
most efficient space reclamation. Last time I looked the docs were a little
hazy on that.
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Smith | 2004-06-16 05:24:30 | Re: Installation problem - mutex_lock/unlock or libpq.so ? |
Previous Message | Iain | 2004-06-16 03:17:57 | Re: VARCHAR -vs- CHAR: huge performance difference? |