MG wrote:
>> I don't think that there were any changes to the template databases.
>>
>> You detected a difference in age(datfrozenxid) - try selecting
>> datfrozenxid itself and you will probably see that it does not
>> change over time.
>
> Yes there are changes.
> db1, db2 and template1 has been
MG wrote:
Yes there are changes.
db1, db2 and template1 has been vacuumed over night, not template0.
4 template0 1.976.569.889
4 template0 1.978.965.587
Not necessarily - the age is the count of how many transactions have
occurred ACROSS ALL DATABASES since the "datfrozenxid" i
07 9:41 AM
Subject: Re: [GENERAL] WARNING: some databases have not been vacuumed in
1953945422 transactions
But I don't understand why there are changes of the databases
template1 and
template0 at all?
I thought they are only templates.
I don't think that there were any changes to the temp
> But I don't understand why there are changes of the databases
> template1 and
> template0 at all?
> I thought they are only templates.
I don't think that there were any changes to the template databases.
You detected a difference in age(datfrozenxid) - try selecting
datfrozenxid
itself and yo
; <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, February 15, 2007 4:57 PM
Subject: Re: [GENERAL] WARNING: some databases have not been vacuumed in
1953945422 transactions
"MG" <[EMAIL PROTECTED]> writes:
Each night a shell script is being executed.
vacuumdb --analyze -U cmduse
"MG" <[EMAIL PROTECTED]> 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 fo
Hello,
we are using PostgreSQL 8.0.3 and have two databases in one cluster. db1 and
db2.
Each night a shell script is being executed.
vacuumdb --analyze -U cmduser db1
vacuumdb --analyze -U cmduser db2
The last weeks the following warnings are given out:
WARNING: some databases have not been v
