Re: some databases have not been vacuumed ... - Mailing list pgsql-admin

From Joshua D. Drake
Subject Re: some databases have not been vacuumed ...
Date
Msg-id 42EE7BA7.6030005@commandprompt.com
Whole thread Raw
In response to some databases have not been vacuumed ...  (FM <dist-list@LEXUM.UMontreal.CA>)
Responses Re: some databases have not been vacuumed ...  (FM <dist-list@LEXUM.UMontreal.CA>)
List pgsql-admin
FM wrote:
> Hello after a vacuum full analyse I received this  :
> WARNING:  some databases have not been vacuumed in 1805294030 transactions
> HINT:  Better vacuum them within 342189617 transactions, or you may have
> a wraparound failure.
>
> I read that it's because i do not vacuum DB very often.
> Now I vacuum every night but the warning remains.
> How can I get rid of this ?

Run a vacuum full on all the database.

>
> Thanks !
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq


--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/

pgsql-admin by date:

Previous
From: FM
Date:
Subject: some databases have not been vacuumed ...
Next
From: "Gregory S. Williamson"
Date:
Subject: Re: some databases have not been vacuumed ...