Re: WARNING: some databases have not been vacuumed in 1953945422 transactions

From: "MG" <pgsql-general(at)carladata(dot)de>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: WARNING: some databases have not been vacuumed in 1953945422 transactions
Date: 2007-02-16 07:59:40
Message-ID: 001201c751a0$6949a600$340aa8c0@geisslinger
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Tom,

thanks for your answer.

But I don't understand why there are changes of the databases template1 and
template0 at all?
I thought they are only templates.

Regards
Michaela

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "MG" <pgsql-general(at)carladata(dot)de>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, February 15, 2007 4:57 PM
Subject: Re: [GENERAL] WARNING: some databases have not been vacuumed in
1953945422 transactions

> "MG" <pgsql-general(at)carladata(dot)de> writes:
>> Each night a shell script is being executed.
>
>> vacuumdb --analyze -U cmduser db1
>> vacuumdb --analyze -U cmduser db2
>
> You need to hit template1 every so often, too. You probably might
> as well just do that every night; it won't take long.
>
>> The last weeks the following warnings are given out:
>> WARNING: some databases have not been vacuumed in 1953945422 =
>> transactions
>
>> Is this critical?
>
> Yes.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2007-02-16 08:57:59 Re: gmake Error "/libpython2.4.a: could not read symbols: Bad value" with ./configure --with-python
Previous Message Bjørn T Johansen 2007-02-16 07:44:21 Re: Problem writing sql statement....