On Tuesday September 21 2004 12:40, Reynard Hilman wrote:
> >Okay, so you have a lot of wide (toasted) fields in whatever table that
> >toast table belongs to ...
>
> Just curious though, why the toast file for this transaction table takes
> the most space (the transaction table itself was only about 10Mb),
> considering there are a few other tables with bigger size (40Mb) than
> this transaction table but do not have toast file that's comparable in
> size to this one.
Not sure this is your problem, but when I have tables whose on-disk size is
significantly larger than the size reported from contrib's dbsize.sql
queries (if that's what you're using), I begin to suspect diskspace
"leakage" due to insufficient postgresql.conf settings for max_fsm_pages
and max_fsm_relations. Those settings need to be bigger than the max
amount of diskspace and number of relations that you'll ever use, or you
may experience this leakage, requiring a "vacuum full" or dump/reload
(alias downtime) to repair.
Ed
