From: | "Davidson, Robert" <robdavid(at)amazon(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Vacuum taking forever |
Date: | 2007-03-22 02:42:40 |
Message-ID: | 8333C841129E074E9F83FC80676BA76E06191083@exchg-sea3-03.ant.amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I am doing a vacuum full on a table that takes up 78 GB of a 79 GB HD. When I couldn't add any more data because of out of disk space errors, I freed up space by dropping other tables in the database. I was able to delete about half the records in the table, but the space consumption did not change. I began a vacuum full on the individual table on 3/15 and the hard drive light hasn't turned off since then.
df -h reports 806 MB free and 79 GB used. Is this enough free space to perform a vacuum? Should I export the table, drop it, and re-import it?
I have implemented data retention policies to keep the amount of data in the table to a more reasonable level in the future and would like to retain what is currently in there, but will not be heartbroken to lose it.
Many thanks for any tips or advice provided.
Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-03-22 02:47:21 | Re: Vacuum taking forever |
Previous Message | George Pavlov | 2007-03-21 22:25:05 | Re: [SQL] Monitor what command is executing at the backend |