Re: vacuum full fills up disk

If the table is going to be read-only you should consider running the
'cluster' command instead.

regards,
thiago lima.

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Wednesday, March 19, 2003 11:57 AM
To: mlennert(at)club(dot)worldonline(dot)be
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] vacuum full fills up disk

"Moritz Lennert" <mlennert(at)club(dot)worldonline(dot)be> writes:
> I have a table with about 10 million tuples of which you can find the
> definition below. I just did an update which filled in the ss_trav_tot

> field for every tuple. Since the database will be read only (no
> updates), I decided to reclaim disk space by running a vacuum full.
> However, the process is slowly but surely filling up my disk. Does
> vacuum full make a copy of the data, or why is this happening ?

It has to temporarily make duplicate index entries for each row it
moves.

You might consider dropping the indexes, vacuum full, rebuild indexes.
(You might also ask yourself if you really need all those indexes...)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html