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". WARNING: relation "public.run" 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". On Mon, Jul 7, 2014 at 1:31 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > 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 >
