Re: Disk space taken
| От | Slavisa Garic |
|---|---|
| Тема | Re: Disk space taken |
| Дата | |
| Msg-id | bcb558900607180555y43ff4af3y1080d8cf252b900e@mail.gmail.com обсуждение исходный текст |
| Ответ на | Disk space taken ("Slavisa Garic" <sgaric@gmail.com>) |
| Ответы |
Re: Disk space taken
|
| Список | pgsql-novice |
Thanks Richard,
Running vacuumdb --full freed the rest of the disk space. Regarding indexes from what you said I understand that if I want to free the space used in the past by indexes and that isn't freed yet (but it should) I should run reindexdb (or reindex in SQL). I did that and another 300MB got freed so thank you for both hints,
Cheers,
Slavisa
Running vacuumdb --full freed the rest of the disk space. Regarding indexes from what you said I understand that if I want to free the space used in the past by indexes and that isn't freed yet (but it should) I should run reindexdb (or reindex in SQL). I did that and another 300MB got freed so thank you for both hints,
Cheers,
Slavisa
On 18/07/06, Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> I've run into an interesting situation (interesting for me at least :-)). I
> have a table that takes up about a 1GB of disk space but has no entries in
> it. I asume this is old stuff data that hasn't been cleaned up properly but
> I have no idea how to get rid of it.
>
> I'll quickly show few things I've done to get the information I have:
I believe that only vacuum full returns disk spaces. Also, if there are any indexs they could be
using disk space also.
http://www.postgresql.org/docs/8.1/interactive/sql-reindex.html
http://www.postgresql.org/docs/8.1/interactive/sql-vacuum.html
Regards,
Richard Broersma Jr.
В списке pgsql-novice по дате отправления: