Thread: WARNING: database must be vacuumed within 8439472 transactions

Maybe you can priorize your worker with a ionice?

----- Mail original -----
De: "Mike Christensen" <mike@kitchenpc.com>
À: "Prabhjot Sheena" <prabhjot.sheena@rivalwatch.com>
Cc: pgsql-admin@postgresql.org, "Forums postgresql" <pgsql-general@postgresql.org>
Envoyé: Lundi 7 Juillet 2014 16:15:18
Objet: Re: [ADMIN] [GENERAL] WARNING: database must be vacuumed within 8439472 transactions


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
criticaldatabase 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

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

Prabhjot Sheena wrote:
> While the vacuumdb --analyze command is running i m getting these messages
> for these tables which might require full vacuum.
>
> WARNING:  relation "public.result" contains more than "max_fsm_pages" pages
> with useful free space
> HINT:  Consider using VACUUM FULL on this relation or increasing the
> configuration parameter "max_fsm_pages".

Ouch.  I had read you were on 9.3 in your first email, but this message
gives me a trip back in time a decade ago -- you're on 8.3!  Clearly you
have had vacuuming issues for a long time.

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