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

From Scott Marlowe
Subject Re: some databases have not been vacuumed ...
Date
Msg-id 1122929975.9182.49.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: some databases have not been vacuumed ...  (FM <dist-list@LEXUM.UMontreal.CA>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: FM
Date:
Subject: Re: some databases have not been vacuumed ...
Next
From: Robert Perry
Date:
Subject: Re: Alter Table vs. Rename/Create/Drop table with plpgsql functions.