X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id DBD389DCBAD for ; Mon, 13 Feb 2006 16:41:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10852-03 for ; Mon, 13 Feb 2006 16:41:07 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.195]) by postgresql.org (Postfix) with ESMTP id 350D69DCBC6 for ; Mon, 13 Feb 2006 16:41:03 -0400 (AST) Received: by uproxy.gmail.com with SMTP id u2so664458uge for ; Mon, 13 Feb 2006 12:41:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=tA+R57U9yHcW+Y1i1kH0xcmwDWv50Esf7mj9H+JMAISFRJ81HvMEep6Fr+yIijA+32fiGpigvxvsPvBJTrVQCq68joE6lfjUcEFMkIxDzK2pVncjoCTJAu/GIi+WbzhU6yNuDkbgkvcMMDGK+VAthFIVadkv7Io40jWHRX/l5Yg= Received: by 10.66.219.10 with SMTP id r10mr1367121ugg; Mon, 13 Feb 2006 12:41:03 -0800 (PST) Received: by 10.66.224.9 with HTTP; Mon, 13 Feb 2006 12:41:03 -0800 (PST) Message-ID: Date: Mon, 13 Feb 2006 20:41:03 +0000 From: Guido Barosio To: juliano.gaio@gmail.com Subject: Re: vacuumdb Cc: pgsql-admin@postgresql.org In-Reply-To: <1e9221d50602130842x1a5d817fi@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25399_17035674.1139863263973" References: <1e9221d50602130842x1a5d817fi@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.387 required=5 tests=[AWL=0.386, HTML_MESSAGE=0.001] X-Spam-Score: 0.387 X-Spam-Level: X-Archive-Number: 200602/166 X-Sequence-Number: 20587 ------=_Part_25399_17035674.1139863263973 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hmmm, AFAIK no, but you can get the age of the databases, and guess if you need to issue a vacuum or not. quote from the documentation (www.postgresql.org -> documentation): SELECT datname, age(datfrozenxid) FROM pg_database; The age column measures the number of transactions from the cutoff XID to the current transaction's XID. With the standard freezing policy, the age column will start at one billion for a freshly-vacuumed database. When the age approaches two billion, the database must be vacuumed again to avoid risk of wraparound failures.Recommended practice is to vacuum each database at least once every half-a-billion (500 million) transactions,so as to provide plenty of safety margin. To help meet this rule, each database-wide VACUUM automatically delivers a warning if there are any pg_database entries showing an age of more than 1.5 billion transactions, for example: play=3D# VACUUM; WARNING: some databases have not been vacuumed in 1613770184 transactions HINT: Better vacuum them within 533713463 transactions, or you may have a wraparound failure. VACUUM Best regards, Guido On 2/13/06, Juliano wrote: > > Hi all, > > There is a way to see vacuumdb last running ? > > tks > > -- > Juliano -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- ------=_Part_25399_17035674.1139863263973 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hmmm, AFAIK no, but you can get the age of the databases, and guess if you = need to issue a vacuum or not.

quote from the documentation (www.postgresql.org -> documentation):

SELECT datname, age(datfrozenxid) FRO=
M pg_database;

The age column meas= ures the number of transactions from the cutoff XID to the current tran= saction's XID. =20

With the standard freezing policy, the age= column will start at one billion for a freshly-vacuumed database.= When the age approaches two billion, the database must be vacuumed again to avoid risk of wraparound failures. Recommended practice is to vacuum each database at least once every half-a-billion (500 million) transactions, so as to provide plenty of safety margin. To help meet this rule, each database-wide VACUUM automatically delivers a wa= rning if there are any pg_database entries s= howing an age of more than 1.5 billion trans= actions, for example:=20

play=3D# VACUUM;
WARNING: some databa= ses have not been vacuumed in 1613770184 transactions
HINT: Better vacu= um them within 533713463 transactions, or you may have a wraparound failure= .
VACUUM

Best regards,
Guido

On 2/13/06, Juliano <juliano.listas@gmail.com> wrote= :
Hi all,

There is a way to see vacuumdb last running ?

tks

--
Juliano



--
/"\ &n= bsp; ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail = ; .
X  - NO Word docs in e-mail .
/ \ ---------------= -------------------------------------------------- ------=_Part_25399_17035674.1139863263973--