DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=cGNNpqcnbE21PyuPbE46KdXDWCXvIfSxNGAu9d9mbQi1jHlzoMzxGQ3JPZD9HugxHW
	CQID2Ir9ovVKX5dE+7+v781mBeWyuQd+RuNq8KOBMOvThIe5zmsBgT6Kd/z6pDk36h7K
	oamiSNU5hK0pPOHjqUltdadlnvZcFPUPWWIzA=
MIME-Version: 1.0
Date: Tue, 31 Mar 2009 13:04:15 -0300
Message-ID: <3a0028490903310904q3df73b6dob4d62511df38563c@mail.gmail.com>
Subject: Vacuum Full
From: Rafael Domiciano <rafael.domiciano@gmail.com>
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary=001636427491c9c98704666c59e5

--001636427491c9c98704666c59e5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello People,

I have some doubts about Vacuum Full. There We go:
1) The Only thing that *Vacuum Full* (Only Full, not Analyze) is to clean
"dead space" on the disc, and reorganize the relation at the physical level?
If it's true, so doing this may speed up *select's*, while the Postgres will
going to do less hit in the disc. I'm right?

2) Doing only *Vacuum Analyze* I have a enlargement of the parameter *
max_fsm_pages*. Does it have any impact in the operation?
Should I increment the value in the conf to be so large than the Vacuum
Verbose shows me?

3) There are differences in performace of Vacuum Full between versions 8.1.4
and 8.3.7?
As soon as possible we are going to migrate the Postgres to 8.3.7, just
waiting the finish of the tests of the software in the new version.

4) The right way to run Vacuum and Reindex is: Vacuum and Reindex or Reindex
and Vacuum?
Running Vacuum I have a Index Bloat, right?! So I have to run Reindex afet
Vacuum?!
If true I'll change the script to make first Vacuum and then Reindex.

5) Does have any way to see how much is left to finish vacuum?
Example:
select * from vacuum_finish;
Relation   Total Bytes    Total Bytes Done      Total Bytes Remaining
Table01    1000             600                          400

Or Something like that!


Thnks for responses,

Rafael Domiciano

--001636427491c9c98704666c59e5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello People,<br><br>I have some doubts about Vacuum Full. There We go:<br>=
1) The Only thing that <b>Vacuum Full</b> (Only Full, not Analyze) is to cl=
ean &quot;dead space&quot; on the disc, and reorganize the relation at the =
physical level?<br>
If it&#39;s true, so doing this may speed up <i>select&#39;s</i>, while the=
 Postgres will going to do less hit in the disc. I&#39;m right?<br><br>2) D=
oing only <b>Vacuum Analyze</b> I have a enlargement of the parameter <i>ma=
x_fsm_pages</i>. Does it have any impact in the operation?<br>
Should I increment the value in the conf to be so large than the Vacuum Ver=
bose shows me?<br><br>3) There are differences in performace of Vacuum Full=
 between versions 8.1.4 and 8.3.7?<br>As soon as possible we are going to m=
igrate the Postgres to 8.3.7, just waiting the finish of the tests of the s=
oftware in the new version.<br>
<br>4) The right way to run Vacuum and Reindex is: Vacuum and Reindex or Re=
index and Vacuum?<br>Running Vacuum I have a Index Bloat, right?! So I have=
 to run Reindex afet Vacuum?!<br>If true I&#39;ll change the script to make=
 first Vacuum and then Reindex.<br>
<br>5) Does have any way to see how much is left to finish vacuum?<br>Examp=
le:<br>select * from vacuum_finish;<br>Relation=A0=A0 Total Bytes=A0=A0=A0 =
Total Bytes Done=A0=A0=A0=A0=A0 Total Bytes Remaining<br>Table01=A0=A0=A0 1=
000=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 600=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 400<br>
<br>Or Something like that!<br><br><br>Thnks for responses,<br><br>Rafael D=
omiciano<br>

--001636427491c9c98704666c59e5--