Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1edYbL-0002jL-9c
	for pgsql-performance@arkaria.postgresql.org; Mon, 22 Jan 2018 09:41:15 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1edYbK-0002EI-LO
	for pgsql-performance@arkaria.postgresql.org; Mon, 22 Jan 2018 09:41:14 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <sk@zsrv.org>)
	id 1edYbK-0002E8-7O
	for pgsql-performance@lists.postgresql.org; Mon, 22 Jan 2018 09:41:14 +0000
Received: from forward100p.mail.yandex.net ([77.88.28.100])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <sk@zsrv.org>)
	id 1edYbC-0002vu-B4
	for pgsql-performance@postgresql.org; Mon, 22 Jan 2018 09:41:12 +0000
Received: from mxback4j.mail.yandex.net (mxback4j.mail.yandex.net
 [IPv6:2a02:6b8:0:1619::10d])
	by forward100p.mail.yandex.net (Yandex) with ESMTP id 22A755101DFD;
	Mon, 22 Jan 2018 12:41:02 +0300 (MSK)
Received: from localhost (localhost [::1])
	by mxback4j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id
 hUifXzWv4R-f10uAGNs;
	Mon, 22 Jan 2018 12:41:01 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail;
 t=1516614061;
	bh=4i2wvCedlOWtuffb7w8wz+VI+1wU/+wwRRiYKyzzYqo=;
	h=From:To:In-Reply-To:References:Subject:Message-Id:Date;
	b=cQQWab/MxL9XPaTn3QVwyb9yBvXoGk8FpbVrnRDUOGFy35YqPLjMf6LXRpaeaEhQe
	 15/alOf5DvED2CJGdnNWjJYAVhDca9ifGSGR29J9TMkyxHRy7irsSnmcMOzTfNbR0N
	 Q5NvvZvpJ/va5jOAR3CdxbFnVGAdgCy/JSvTMZmQ=
Authentication-Results: mxback4j.mail.yandex.net; dkim=pass header.i=@zsrv.org
Received: by web46o.yandex.ru with HTTP;
	Mon, 22 Jan 2018 12:41:00 +0300
From: Sergei Kornilov <sk@zsrv.org>
To: pavan95 <pavan.postgresdba@gmail.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
In-Reply-To: <1516601350338-0.post@n3.nabble.com>
References: <46D83427.60001@livedatagroup.com>
 <1516601350338-0.post@n3.nabble.com>
Subject: Re: 8.2 Autovacuum BUG ?
MIME-Version: 1.0
Message-Id: <987851516614060@web46o.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Mon, 22 Jan 2018 12:41:00 +0300
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

Hello
How big is database?
Please show result of this query: select * from pg_stat_activity where query like 'autovacuum%';
I think here is running antiwraparound autovacuum. In this case all is normal, antiwraparound will produce a lot of WAL and this is necessary to continue database working.

PS: please note postgresql 9.1 is EOL.

regards, Sergei