Re: vacuum full fills up disk - solved
| От | Moritz Lennert |
|---|---|
| Тема | Re: vacuum full fills up disk - solved |
| Дата | |
| Msg-id | 83cc50c0f6898eefdba78a1eccc1e29b обсуждение исходный текст |
| Ответ на | Re: vacuum full fills up disk (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-general |
Moritz Lennert said: >> "Moritz Lennert" <mlennert@club.worldonline.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. > > Thanks, I'll try that. > That did the trick: I'm down to 25% disk usage from 75% before ! Thanks for the hint, Moritz
В списке pgsql-general по дате отправления: