X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (unknown [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CD01F9FB2F4 for ; Wed, 30 Aug 2006 11:10:55 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 32393-05 for ; Wed, 30 Aug 2006 11:10:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 034839FB310 for ; Wed, 30 Aug 2006 10:48:25 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7UDmM80026746; Wed, 30 Aug 2006 09:48:23 -0400 (EDT) To: "Nigel Bishop" cc: pgsql-admin@postgresql.org Subject: Re: Some advice required please In-reply-to: <72558D9A7573814BB4082A28843E03D403546E3F@intyodc01.uk.ioko365.com> References: <72558D9A7573814BB4082A28843E03D403546E3F@intyodc01.uk.ioko365.com> Comments: In-reply-to "Nigel Bishop" message dated "Wed, 30 Aug 2006 11:34:49 +0100" Date: Wed, 30 Aug 2006 09:48:22 -0400 Message-ID: <26745.1156945702@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/329 X-Sequence-Number: 22872 "Nigel Bishop" writes: > Selecting from pg_database shows the following: > datname | datvacuumxid | datfrozenxid > ----------------+--------------+-------------- > template1 | 2160549932 | 1086808109 > template0 | 427 | 427 > live01.db | 427 | 427 > stage01.db | 2153231186 | 1079489364 The numbers for template1 and stage01.db look reasonable (but perhaps you just recently vacuumed them?). What the message is probably complaining about is that live01.db has seemingly never been vacuumed. You can ignore template0, it's not supposed to be touched, but the others all need vacuuming every so often. > Could someone advise me on how to reset the datvacuumxid on the > template1 DB (I don't think it should be this high), also is the message > about data loss really implying that we may have lost data? Yes, otherwise we'd not bother to emit it. regards, tom lane