Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 7489963246E
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 19 Jan 2009 11:54:35 -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 18083-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 19 Jan 2009 11:54:32 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from rv-out-0506.google.com (rv-out-0506.google.com
 [209.85.198.233])
	by mail.postgresql.org (Postfix) with ESMTP id A839F632439
	for <pgsql-admin@postgresql.org>; Mon, 19 Jan 2009 11:54:32 -0400 (AST)
Received: by rv-out-0506.google.com with SMTP id b25so2785408rvf.43
	for <pgsql-admin@postgresql.org>; Mon, 19 Jan 2009 07:54:30 -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
	:content-transfer-encoding:content-disposition:references;
	bh=qVGFlaC+b979hp62tgLyG/VMdhJl2xdQpcBKlVXX+T0=;
	b=HmE5wPOb1UfkmDDSIA87B1UxTfub3BuDJDh4k8PBEa+QqreTM3Q08+2/D6mq+GSbGf
	0bPcZ3MUOvtwoDI/JKUBk6ghQH81Zb7wuE940/LWN8CO8CeZRJRRAd449ynoI2dwNSHo
	VSBseay839DEoTfkt8ahVLCVwBxcvN4TrPsq0=
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:content-transfer-encoding:content-disposition
	:references;
	b=eaByvuj6RMKbWEoRxMtSIpdsh1l34+RQVfktzxr7MXpAu5KS/r4GvQG1kZtDGqETY7
	AtIcGT0zceRlqHINcYXYegguFKuR/L5SXuRjFffa18YOJpMT02d3gY9HtkzuDhHRkkjE
	cGAczeeVf/UD+oMvKYJsmXpo4VSOA5K+DQazc=
Received: by 10.114.13.10 with SMTP id 10mr4135436wam.219.1232380470725;
	Mon, 19 Jan 2009 07:54:30 -0800 (PST)
Received: by 10.114.149.5 with HTTP; Mon, 19 Jan 2009 07:54:30 -0800 (PST)
Message-ID: <dcc563d10901190754o4c8f74eeidad1b52cf2e73356@mail.gmail.com>
Date: Mon, 19 Jan 2009 08:54:30 -0700
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "BRAHMA PRAKASH TIWARI" <prakashr2n5@gmail.com>
Subject: Re: tuning tips, speed problem
Cc: "Francesco Andreozzi" <francesco.andreozzi@gamestorm.it>,
	pgsql-admin@postgresql.org
In-Reply-To: <2acc2c820901190435m4062f8d3v1e6099f32ed009af@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20090116161802.v6tj5jmhw0c80sow@webmail.gamestorm.it>
	<2acc2c820901190435m4062f8d3v1e6099f32ed009af@mail.gmail.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200901/62
X-Sequence-Number: 31109

On Mon, Jan 19, 2009 at 5:35 AM, BRAHMA PRAKASH TIWARI
<prakashr2n5@gmail.com> wrote:
> Hi Francesco
>
> most probabely this is due to the auto vacuum option on and if auto vacuum
> is on then the in condition of high transaction on database it slows the
> speed of the hole database.Set it off in postgres.conf and vacuum and
> reindex transactional tables manualy with in  every two million
> transactions.
> like
> vacuum full <table name>;
> reindex table <table name>;

Except for certain circumstances vacuum full should be avoided and
vacuum (regular) used in its place until it is proven ineffective.

Also, it is usually far better to turn up the
autovacuum_vacuum_cost_delay to 10 or 20 and let autovacuum do its
job.  Unless you have a very starved I/O subsystem autovacuum with
cost delay of 20 should have almost no noticeable effect on a
transactional database.