Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 7E09B9FB302
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Mon, 15 Jan 2007 10:23:36 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024)
	with ESMTP id 85575-09 for <pgsql-sql-postgresql.org@postgresql.org>;
	Mon, 15 Jan 2007 10:23:20 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from web30013.mail.mud.yahoo.com (web30013.mail.mud.yahoo.com
	[209.191.69.30]) by postgresql.org (Postfix) with SMTP id CED169FB258
	for <pgsql-sql@postgresql.org>; Mon, 15 Jan 2007 10:23:25 -0400 (AST)
Received: (qmail 6704 invoked by uid 60001); 15 Jan 2007 14:23:24 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=j+4YrNPk8xiku7EJfrvzfX8LgvRdeEj1mq/6fzTQA1CuNbpLTpgF92/ZmB2BHqJLr4TO11AYw4rQFiyuOy81iieJI706w7RPoBPG8qgmTXkeOy5tT859YeQa1eJ/nbY8kF8BH9E4zbial0AiVOYn/LpVNvHw55X2doUp2x2664s=;
X-YMail-OSG: 
 Wt8DUycVM1ncvkn91Vv9kz.jCBkleW3KfzC8AsLEwOQbQmSTZk5yRPaYlnbYymhv9OnQsy14jRKM2jadu_CEjqAVZl96nogxH2Z0_wZMceD3bp28_txMrwiaRyrlmMnbzwg9k.nD2Q--
Received: from [200.161.5.135] by web30013.mail.mud.yahoo.com via HTTP;
	Mon, 15 Jan 2007 06:23:24 PST
X-Mailer: YahooMailRC/368.3 YahooMailWebService/0.6.132.7
Date: Mon, 15 Jan 2007 06:23:23 -0800 (PST)
From: Mario Behring <mariobehring@yahoo.com>
Subject: vacuum process taking more than 33 hours
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1589075351-1168871003=:5826"
Message-ID: <2529.5826.qm@web30013.mail.mud.yahoo.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200701/46
X-Sequence-Number: 27198

--0-1589075351-1168871003=:5826
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,=0A=0AI've executed a VACUUM FULL on a database 33GB in size. The pr=
ocess was going fine until it reached a index (I guess it's an index) and t=
here it stopped for more than 30 hours...........the whole weekend......=0A=
=0AI'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 k=
now to be the largest one. I have some questions though:=0AWill the TRUNCAT=
E free disk space?Can I run this command and let the openNMS software runni=
ng at the same time? The ONMS product will certainly try to execute INCLUDE=
S and such.If the TRUNCATE indeed free disk space, what should I do next, r=
eindex, vacuum ??=0A=0AAlso, what else can I do to avoid this kind of probl=
em? Would a REINDEX fix the problem and let the VACUUM command finish?=0A=
=0APlease advise.=0A=0AThank you.=0A=0ABest regards,=0A=0AMario Behring=0A=
=0A=0A=0A=0A =0A___________________________________________________________=
_________________________=0ATV dinner still cooling? =0ACheck out "Tonight'=
s Picks" on Yahoo! TV.=0Ahttp://tv.yahoo.com/
--0-1589075351-1168871003=:5826
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:arial,helvetica,sans-serif;font-size:10p=
t"><div>Hi all,<br><br>I've executed a VACUUM FULL on a database 33GB in si=
ze. The process was going fine until it reached a index (I guess it's an in=
dex) and there it stopped for more than 30 hours...........the whole weeken=
d......<br><br>I've canceled it but I desperately need to free some space a=
t the server's disk. I was thinking about using the TRUNCATE statement at t=
he table I know to be the largest one. I have some questions though:<br><ul=
><li>Will the TRUNCATE free disk space?</li><li>Can I run this command and =
let the openNMS software running at the same time? The ONMS product will ce=
rtainly try to execute INCLUDES and such.</li><li>If the TRUNCATE indeed fr=
ee disk space, what should I do next, reindex, vacuum ??<br></li></ul><br>A=
lso, what else can I do to avoid this kind of problem? Would a REINDEX fix =
the problem and
 let the VACUUM command finish?<br><br>Please advise.<br><br>Thank you.<br>=
<br>Best regards,<br><br>Mario Behring<br></div></div><br>=0A=0A<hr size=3D=
1>Finding fabulous fares is fun.<br><a href=3D"http://farechase.yahoo.com/p=
romo-generic-14795097;_ylc=3DX3oDMTFtNW45amVpBF9TAzk3NDA3NTg5BF9zAzI3MTk0OD=
EEcG9zAzEEc2VjA21haWx0YWdsaW5lBHNsawNxMS0wNw--=0A">Let Yahoo! FareChase sea=
rch your favorite travel sites</a> to find flight and hotel bargains.</body=
></html>
--0-1589075351-1168871003=:5826--