Re: [ADMIN] some databases have not been vacuumed ...

2005-08-02 Thread Tom Lane
Christopher Browne <[EMAIL PROTECTED]> writes: > The problem is likely that the "old tuples" are in some database not > being vacuumed. template1 is a likely candidate; do a plain VACUUM on > that and the message may go away. It's not really necessary to guess about which database(s) are triggeri

Re: [ADMIN] some databases have not been vacuumed ...

2005-08-02 Thread Christopher Browne
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] ("Joshua D. Drake") transmitted: > 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 t

Re: [ADMIN] some databases have not been vacuumed ...

2005-08-01 Thread Scott Marlowe
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 ? > v

Re: [ADMIN] some databases have not been vacuumed ...

2005-08-01 Thread FM
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 bee

Re: [ADMIN] some databases have not been vacuumed ...

2005-08-01 Thread Gregory S. Williamson
:[ADMIN] some databases have not been vacuumed ... 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 beca

Re: [ADMIN] some databases have not been vacuumed ...

2005-08-01 Thread Joshua D. Drake
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

[ADMIN] some databases have not been vacuumed ...

2005-08-01 Thread FM
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 eve