| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Prabhjot Sheena <prabhjot(dot)sheena(at)rivalwatch(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |
| Date: | 2014-07-07 20:31:44 |
| Message-ID: | 20140707203144.GG6390@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prabhjot Sheena | 2014-07-07 20:44:32 | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |
| Previous Message | Frank Pinto | 2014-07-07 20:31:40 | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prabhjot Sheena | 2014-07-07 20:44:32 | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |
| Previous Message | Frank Pinto | 2014-07-07 20:31:40 | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |