From: Mario Behring <mariobehring@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: vacuum process taking more than 33 hours
Date: Mon, 15 Jan 2007 06:23:23 -0800 (PST)
Message-ID: <2529.5826.qm@web30013.mail.mud.yahoo.com> (raw)
Hi all,
I've executed a VACUUM FULL on a database 33GB in size. The process was going fine until it reached a index (I guess it's an index) and there it stopped for more than 30 hours...........the whole weekend......
I've canceled it but I desperately need to free some space at the server's disk. I was thinking about using the TRUNCATE statement at the table I know to be the largest one. I have some questions though:
Will the TRUNCATE free disk space?Can I run this command and let the openNMS software running at the same time? The ONMS product will certainly try to execute INCLUDES and such.If the TRUNCATE indeed free disk space, what should I do next, reindex, vacuum ??
Also, what else can I do to avoid this kind of problem? Would a REINDEX fix the problem and let the VACUUM command finish?
Please advise.
Thank you.
Best regards,
Mario Behring
____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mariobehring@yahoo.com
Subject: Re: vacuum process taking more than 33 hours
In-Reply-To: <2529.5826.qm@web30013.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox