From: Bill Moran <wmoran@potentialtech.com>
To: Scott Whitney <scott@journyx.com>
Cc: Mike Christensen <mike@kitchenpc.com>
Cc: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: Forums postgresql <pgsql-general@postgresql.org>
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
Date: Mon, 7 Jul 2014 16:27:18 -0400
Message-ID: <20140707162718.f1d66ba80aaea1d3ef3d5f3e@potentialtech.com> (raw)
In-Reply-To: <pbwq0jvbgjg1nw5hnhe18aqe.1404764557197@email.android.com>
References: <pbwq0jvbgjg1nw5hnhe18aqe.1404764557197@email.android.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: wmoran@potentialtech.com, scott@journyx.com, mike@kitchenpc.com, prabhjot.sheena@rivalwatch.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
In-Reply-To: <20140707162718.f1d66ba80aaea1d3ef3d5f3e@potentialtech.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox