Thread: some databases have not been vacuumed ...
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 ? Thanks !
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/
Did you vacuum the template1 database as well as whatever databases you have created ? HTH, Greg Williamson DBA GlobeXplorer LLC -----Original Message----- From: pgsql-admin-owner@postgresql.org on behalf of FM Sent: Mon 8/1/2005 12:35 PM To: Mailing List Postgres-Admin Cc: Subject: [ADMIN] some databases have not been vacuumed ... 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 ? Thanks ! ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq !DSPAM:42ee7af1176271374616439!
I vacumm all DB ...except... postgres ones. I"ll do a vacuum -all tonight What is you vacuum strategy ? vacuum everyday and vacuum full analyse ervery week ? thanks ! Joshua D. Drake wrote: > 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 > > >
No. Vacuum full should not be necessary on a properly configured server. See: http://www.postgresql.org/docs/8.0/static/maintenance.html On Mon, 2005-08-01 at 15:51, FM wrote: > I vacumm all DB ...except... postgres ones. > > I"ll do a vacuum -all tonight > > What is you vacuum strategy ? > vacuum everyday and vacuum full analyse ervery week ? > > thanks ! > > > Joshua D. Drake wrote: > > 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 > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster
In an attempt to throw the authorities off his trail, jd@commandprompt.com ("Joshua D. Drake") transmitted: > 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. That seems overkill. The problem is likely that the "old tuples" are in some database not being vacuumed. template1 is a likely candidate; do a plain VACUUM on that and the message may go away. It can be *possible* for the issue to be with template0, if it had at some point been open for modification. If that is the case, it is a good idea to: - Unlock template0 (via table pg_database) - Run VACUUM FREEZE on template0 - Relock it -- (format nil "~S@~S" "cbbrowne" "gmail.com") http://linuxdatabases.info/info/slony.html "You think you know when you can learn, are more sure when you can write, even more when you can teach, but certain when you can program." -- Alan Perlis
Christopher Browne <cbbrowne@acm.org> writes: > The problem is likely that the "old tuples" are in some database not > being vacuumed. template1 is a likely candidate; do a plain VACUUM on > that and the message may go away. It's not really necessary to guess about which database(s) are triggering the message: a quick look in pg_database will tell you. See TFM: http://www.postgresql.org/docs/8.0/static/maintenance.html#VACUUM-FOR-WRAPAROUND regards, tom lane