Re: VARCHAR -vs- CHAR: huge performance difference? - Mailing list pgsql-admin

From Iain
Subject Re: VARCHAR -vs- CHAR: huge performance difference?
Date
Msg-id 009601c4535e$3e8d10c0$7201a8c0@mst1x5r347kymb
Whole thread Raw
In response to VARCHAR -vs- CHAR: huge performance difference?  ("C. Bensend" <benny@bennyvision.com>)
List 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.


pgsql-admin by date:

Previous
From: "Iain"
Date:
Subject: Re: VARCHAR -vs- CHAR: huge performance difference?
Next
From: "Scott Marlowe"
Date:
Subject: Re: VARCHAR -vs- CHAR: huge performance difference?