Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-general-owner+M206803=pgsql-general-arkari@postgresql.org>)
 id 1X4FVe-0006UF-Jg
 for pgsql-general@arkaria.postgresql.org; Mon, 07 Jul 2014 20:27:34 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-general-owner+M206803=pgsql-general-arkari@postgresql.org>)
 id 1X4FVd-0006C0-2t
 for pgsql-general@arkaria.postgresql.org; Mon, 07 Jul 2014 20:27:33 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <wmoran@potentialtech.com>)
 id 1X4FVa-00065Q-1t; Mon, 07 Jul 2014 20:27:30 +0000
Received: from virtual1.potentialtech.com ([69.25.178.43]
 helo=mail.potentialtech.com)
 by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <wmoran@potentialtech.com>)
 id 1X4FVW-0002EX-Oc; Mon, 07 Jul 2014 20:27:28 +0000
Received: from working (c-67-165-86-201.hsd1.pa.comcast.net [67.165.86.201])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.potentialtech.com (Postfix) with ESMTPSA id 054D5224B1E;
 Mon,  7 Jul 2014 16:27:23 -0400 (EDT)
Date: Mon, 7 Jul 2014 16:27:18 -0400
From: Bill Moran <wmoran@potentialtech.com>
To: Scott Whitney <scott@journyx.com>
Cc: Mike Christensen <mike@kitchenpc.com>, Prabhjot Sheena
 <prabhjot.sheena@rivalwatch.com>, "pgsql-admin@postgresql.org"
 <pgsql-admin@postgresql.org>, Forums postgresql
 <pgsql-general@postgresql.org>
Subject: Re: [ADMIN] WARNING: database must be vacuumed within
 8439472 transactions
Message-Id: <20140707162718.f1d66ba80aaea1d3ef3d5f3e@potentialtech.com>
In-Reply-To: <pbwq0jvbgjg1nw5hnhe18aqe.1404764557197@email.android.com>
References: <pbwq0jvbgjg1nw5hnhe18aqe.1404764557197@email.android.com>
X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.22; amd64-portbld-freebsd9.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.6 (--)
List-Archive: <http://archives.postgresql.org/pgsql-general>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-general.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@postgresql.org>
List-Post: <mailto:pgsql-general@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-general>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
X-Mailing-List: pgsql-general
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

On Mon, 7 Jul 2014 15:22:44 -0500 (CDT) Scott Whitney <scott@journyx.com> wrote:

> It does say a FULL vacuum, and that you are not doing.

You're confusing terminology.  VACUUM FULL is not the same as
a "full database vacuum".  The latter is simply expressing that
vacuuming individual tables won't fix the problem.  A VACUUM
FULL is not required.

You really just need to wait it out.  Although at the rate the
number seems to be dropping, you may be in for trouble.

> 
> <div>-------- Original message --------</div><div>From: Mike Christensen <mike@kitchenpc.com> </div><div>Date:07/07/2014  3:17 PM  (GMT-06:00) </div><div>To: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com> </div><div>Cc: pgsql-admin@postgresql.org,Forums postgresql <pgsql-general@postgresql.org> </div><div>Subject: Re: [ADMIN] [GENERAL] WARNING: database must be vacuumed within 8439472 transactions </div><div>
> </div>Sounds like you just have to wait until it finishes..
> 
> 
> On Mon, Jul 7, 2014 at 12:56 PM, Prabhjot Sheena <prabhjot.sheena@rivalwatch.com> wrote:
> Hello
>        We are using postgresql 8.3 database for last 5 yrs for this production database and its running fine. This is our critical database which runs 24*7. This weekend we started getting these messages
> 
> HINT:  To avoid a database shutdown, execute a full-database VACUUM.
> WARNING:  database  must be vacuumed within 8439472 transactions
> 
> i am currently running this command
> 
> vacuumdb --analyze db
> 
> while this command is running i m still getting these messages 
> 
> WARNING:  database  must be vacuumed within 2645303 transactions. 
> 
> The value of number of transactions is going down every minute 
> 
> Can anyone tell me what is the best way to sort up this issue. 
> 
> Thanks
> Avi
> 
> 
> 
> 


-- 
Bill Moran <wmoran@potentialtech.com>


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general