| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Shridhar Polas <shridharpolas(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Space occupied by Postgres index. |
| Date: | 2010-11-30 17:28:41 |
| Message-ID: | 20101130172841.GK19162@aart.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Nov 30, 2010 at 10:56:53PM +0530, Shridhar Polas wrote:
> Hi,
>
>
>
> I am facing a problem where indexes creates on some tables are occupying
> huge space on disk and it seems to me that this space is not getting
> reclaimed even when there are very few record in an associated table.
>
>
>
> When I ran full vacuum the disk space was reclaimed occupied by tables but
> not by disk space occupied by indexes.
>
>
>
> Can somebody please tell me when disk space occupied by Postgres index is
> reclaimed, without performing re-indexing on those tables?
>
>
>
> Thanks,
>
> Shridhar
>
VACUUM FULL will cause index bloat. You will need to REINDEX to
recover the space. Note, you should not really need to use VACUUM
FULL in a normal correctly configured system.
Cheers,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 100-eti | 2010-11-30 17:37:51 | Re: Postgres service won't start, doesn't log any errors |
| Previous Message | Shridhar Polas | 2010-11-30 17:26:53 | Space occupied by Postgres index. |