From: | "Slavisa Garic" <sgaric(at)gmail(dot)com> |
---|---|
To: | "Richard Broersma Jr" <rabroersma(at)yahoo(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Disk space taken |
Date: | 2006-07-18 12:55:39 |
Message-ID: | bcb558900607180555y43ff4af3y1080d8cf252b900e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
On 18/07/06, Richard Broersma Jr <rabroersma(at)yahoo(dot)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.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2006-07-18 14:43:14 | Re: Disk space taken |
Previous Message | Richard Broersma Jr | 2006-07-18 12:34:05 | Re: Disk space taken |