Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 2F19664FD32
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 26 Nov 2008 13:21:45 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 02517-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 26 Nov 2008 13:21:42 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from gv-out-0910.google.com (gv-out-0910.google.com
 [216.239.58.189])
	by mail.postgresql.org (Postfix) with ESMTP id AE303650317
	for <pgsql-admin@postgresql.org>; Wed, 26 Nov 2008 13:21:40 -0400 (AST)
Received: by gv-out-0910.google.com with SMTP id i36so231214gve.7
	for <pgsql-admin@postgresql.org>; Wed, 26 Nov 2008 09:21:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=UkK/+epOerMxI611gLsgTTd0zVUaPJzPdTQ+Yzc/GoE=;
	b=KhS1Ktv26Tsy0o/L7qr/25mA0hpINRUkE5mkeetSp0MGf5Xb/w0C+L7FZYOeSgibyD
	u1IaXZkFMOaeTJsGsQIObxd2aTQpH775wngAS7JU/x///FcoOzu8kDdJ63o8TlPYrWO/
	0G97doKazGrsmsQCMr0OOAU3TDlQ7s74sLVo0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:references;
	b=A1qUilgouuze8DEtMfH4XMZUPRnXbyNKZdM5IKdLS7FTqGkRPuqOW6dDU/pvnlT63N
	5x2bRHKOJwAl3sVN8EawuZHr86RzEa9/VllKPRhSezN7CzyWb9QJu1APFEmkeaPztxkC
	YPLq2x5ZAJ3vxKouK9J/k7eNi2rH8PaxZXqDY=
Received: by 10.86.79.19 with SMTP id c19mr3969308fgb.26.1227720099608;
	Wed, 26 Nov 2008 09:21:39 -0800 (PST)
Received: by 10.86.83.10 with HTTP; Wed, 26 Nov 2008 09:21:39 -0800 (PST)
Message-ID: <3a0028490811260921l5d6aac06v54dca32aae672b97@mail.gmail.com>
Date: Wed, 26 Nov 2008 15:21:39 -0200
From: "Rafael Domiciano" <rafael.domiciano@gmail.com>
To: "Scott Marlowe" <scott.marlowe@gmail.com>
Subject: Re: Vacuum Problems
Cc: "Rafael Martinez" <r.m.guerrero@usit.uio.no>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <dcc563d10811260740m69f8969bt36be6ae675620dcb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7774_24632735.1227720099579"
References: <3a0028490811260543x74d02719w775a457999cfc74@mail.gmail.com>
	<492D5C87.5090505@usit.uio.no>
	<3a0028490811260700w6e8d9d86o24effbe0bea2bddb@mail.gmail.com>
	<dcc563d10811260740m69f8969bt36be6ae675620dcb@mail.gmail.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200811/152
X-Sequence-Number: 30806

------=_Part_7774_24632735.1227720099579
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm not using autovacuum. Regular vacuum goes ok.To see the last 10 lines of
verbose i will need to run vacuum tonight

If a run a reindex before the vacuum full, increase the "speed" of doing
vacuum? I found something about it googling.

2008/11/26 Scott Marlowe <scott.marlowe@gmail.com>

> 2008/11/26 Rafael Domiciano <rafael.domiciano@gmail.com>:
> > The database has around 40 Gb.
> > If I not use vacuum full everyday the database get very slow.
> >
> > There is no deadlock on the database.
>
> You didn't mention  if you were using autovacuum or not.  You also
> didn't mention whether or not you'd tried regular vacuums if for some
> reason you can't use autovacuum.  Vacuum full is very intrusive and
> can cause index bloat.  It's more of a repair operation than a routine
> maintenance one.
>
> What do the last 10 or so lines of vacuum verbose run as a super user say?
>

------=_Part_7774_24632735.1227720099579
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;m not using autovacuum. Regular vacuum goes ok.<div>To see the last 10 lines of verbose i will need to run vacuum tonight</div><div><br></div><div>If a run a reindex before the vacuum full, increase the &quot;speed&quot; of doing vacuum? I found something about it googling.<br>
<br><div class="gmail_quote">2008/11/26 Scott Marlowe <span dir="ltr">&lt;<a href="mailto:scott.marlowe@gmail.com">scott.marlowe@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2008/11/26 Rafael Domiciano &lt;<a href="mailto:rafael.domiciano@gmail.com">rafael.domiciano@gmail.com</a>&gt;:<br>
<div class="Ih2E3d">&gt; The database has around 40 Gb.<br>
&gt; If I not use vacuum full everyday the database get very slow.<br>
&gt;<br>
&gt; There is no deadlock on the database.<br>
<br>
</div>You didn&#39;t mention &nbsp;if you were using autovacuum or not. &nbsp;You also<br>
didn&#39;t mention whether or not you&#39;d tried regular vacuums if for some<br>
reason you can&#39;t use autovacuum. &nbsp;Vacuum full is very intrusive and<br>
can cause index bloat. &nbsp;It&#39;s more of a repair operation than a routine<br>
maintenance one.<br>
<br>
What do the last 10 or so lines of vacuum verbose run as a super user say?<br>
</blockquote></div><br></div>

------=_Part_7774_24632735.1227720099579--