Date: Mon, 7 Jul 2014 16:31:44 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
 Forums postgresql <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] WARNING: database must be vacuumed within 8439472
 transactions
Message-ID: <20140707203144.GG6390@eldon.alvh.no-ip.org>
References: 
 <CAOf_bQZdiQFrQtvyh5SCzQc63GZWYt=D=oOu4f2mgBKVAO9tEA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAOf_bQZdiQFrQtvyh5SCzQc63GZWYt=D=oOu4f2mgBKVAO9tEA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Prabhjot Sheena 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

Did you omit the database name here, or is it really an empty string?
Make sure you vacuum exactly the database mentioned there.  Autovacuum
should be doing it, though, but perhaps it's dying for some reason and
it can't vacuum one table in particular.  You should check your log for
errors.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


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