From: Kevin Grittner <kgrittn@ymail.com>
To: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John R Pierce <pierce@hogranch.com>
Cc: pgsql <pgsql-general@postgresql.org>
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
Date: Tue, 8 Jul 2014 07:22:39 -0700
Message-ID: <1404829359.42485.YahooMailNeo@web122306.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAOf_bQZOzUfLSe9cQJ6hLJ9UuVhbCTQFGm=hm5df3GZoZnMcRg@mail.gmail.com>
References: <llqby44xt4iugpyxywv1ecdx.1404767140640@email.android.com>
<CAOf_bQbR8nLQ4-yJ9bqw8P980NeVJYVSeK=FTYJctazYr0kuWw@mail.gmail.com>
<53BB25E4.5080400@hogranch.com>
<13414.1404774893@sss.pgh.pa.us>
<CAOf_bQZOzUfLSe9cQJ6hLJ9UuVhbCTQFGm=hm5df3GZoZnMcRg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
Prabhjot Sheena <prabhjot.sheena@rivalwatch.com> wrote:
> So this is what i did but my problem is still not going away.
>
> i shutdown the database and started it in single user mode and
> issued command vacuum full
>
> The command completed but the issue still exists
That is to be expected. The VACUUM FULL command is not useful in
this situation. You need to do a normal VACUUM of the full
database, which is something completely different. You might want
to read this blog page for a discussion of this:
http://rhaas.blogspot.com/2014/03/vacuum-full-doesnt-mean-vacuum-but.html
If you can upgrade to a supported version you will find many
improvements to VACUUM in general and autovacuum in particular, but
that's probably something to consider after you dig yourself out of
the hole you're in now due to inadequate vacuuming.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
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: kgrittn@ymail.com, prabhjot.sheena@rivalwatch.com, tgl@sss.pgh.pa.us, pierce@hogranch.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
In-Reply-To: <1404829359.42485.YahooMailNeo@web122306.mail.ne1.yahoo.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