That actually sounds terrifying. I'd throw up a caching layer ASAP to try to decrease the speed those transactions are happening.
Frank On Mon, Jul 7, 2014 at 2:25 PM, Nicolas Zin < nicolas....@savoirfairelinux.com> wrote: > Maybe you can priorize your worker with a ionice? > > ----- Mail original ----- > De: "Mike Christensen" <m...@kitchenpc.com> > À: "Prabhjot Sheena" <prabhjot.she...@rivalwatch.com> > Cc: pgsql-ad...@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.she...@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 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 > > 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 > > > > > > > > > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
