From: | "Bryan Murphy" <bryan(dot)murphy(at)gmail(dot)com> |
---|---|
To: | "Joao Miguel Ferreira" <joao(dot)mc(dot)ferreira(at)criticalsoftware(dot)com> |
Cc: | Ben <bench(at)silentmedia(dot)com>, "pgsql general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Index Usage |
Date: | 2007-10-17 13:28:26 |
Message-ID: | bd8531800710170628j5da588c7l6147241f936f0baa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/17/07, Joao Miguel Ferreira <joao(dot)mc(dot)ferreira(at)criticalsoftware(dot)com> wrote:
> If your intention is to eliminate the unused indexes rows you should run
> 'vaccum' and/or 'vacuum full' and/or 'reindex'.
>
> This also has the consequence of freing filesystem space and returning
> it back to the OS.
>
> Check it out here:
>
> http://www.postgresql.org/docs/8.1/static/maintenance.html
>
> chapters 22.1, 22.2 and 22.3
>
> I use:
>
> VACUUM FULL ANALYZE;
> REINDEX INDEX yourIndex;
> REINDEX TABLE yourTable
>
> it works just great for me.
>
> Cheers
> joao
That's not my intention at all. My intention is to justify the
validity of each index in our database. Some indexes have snuck in
that I find of questionable value, and I want the data to backup my
intuition.
Anyway, I'll look into the pg_stat* tables and see if those give me
the data I want. Thanks for the advice guys!
Bryan
From | Date | Subject | |
---|---|---|---|
Next Message | Joris Dobbelsteen | 2007-10-17 13:56:00 | Re: newbie question |
Previous Message | Bill Moran | 2007-10-17 12:53:25 | Re: Possibilities of Fine Grained Access Control? |