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 43C249DC817 for ; Thu, 5 Jan 2006 13:30:21 -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 36095-10 for ; Thu, 5 Jan 2006 13:30:19 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.206]) by postgresql.org (Postfix) with ESMTP id 542E29DC812 for ; Thu, 5 Jan 2006 13:30:16 -0400 (AST) Received: by nproxy.gmail.com with SMTP id o60so38822nfa for ; Thu, 05 Jan 2006 09:30:14 -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=EDEdatGAbF59k1caw2G3W+z03d8vlKNqLvskn6hWQ3u90mBL1QidWYAPOv3DRApz9xujCDGTpFogq6e8JQKdXfVObxewGk+IZHwlBB0SJssQZH6d1SOleYmg5jbNDEC9ddBaPCka3XOOuj3gX5f4s1aumh4TzHDag+qyQ4pZ90A= Received: by 10.48.254.2 with SMTP id b2mr705422nfi; Thu, 05 Jan 2006 09:30:13 -0800 (PST) Received: by 10.49.2.17 with HTTP; Thu, 5 Jan 2006 09:30:13 -0800 (PST) Message-ID: Date: Thu, 5 Jan 2006 17:30:13 +0000 From: Guido Barosio To: Jaime Casanova Subject: Re: Vacuum is needed or not? Cc: Szabolcs BALLA , postgre In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29823_13676893.1136482213120" References: <1136466721.4221.39.camel@bh> <1136475086.4221.48.camel@bh> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.08 required=5 tests=[AWL=0.079, HTML_MESSAGE=0.001] X-Spam-Score: 0.08 X-Spam-Level: X-Archive-Number: 200601/72 X-Sequence-Number: 20160 ------=_Part_29823_13676893.1136482213120 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline http://www.postgresql.org/docs/8.0/interactive/maintenance.html Read all, in order to understand the following quote: " Since periodic VACUUM runs are needed anyway for the reasons described earlier, it's unlikely that any table would not be vacuumed for as long as = a billion transactions. But to help administrators ensure this constraint is met, VACUUM stores transaction ID statistics in the system table pg_databas= e. In particular, the datfrozenxid column of a database's pg_database row is updated at the completion of any database-wide VACUUM operation (i.e., VACUUM that does not name a specific table). The value stored in this field is the freeze cutoff XID that was used by that VACUUM command. All normal XIDs older than this cutoff XID are guaranteed to have been replaced by FrozenXID within that database. A convenient way to examine this informatio= n is to execute the query SELECT datname, age(datfrozenxid) FROM pg_database; " Best wishes, Guido On 1/5/06, Jaime Casanova wrote: > > On 1/5/06, Szabolcs BALLA wrote: > > > > > VACUUM is needed at least every billion transactions... > > execute it in a > > script periodically... if you are in doubt if you need > VACUUM then you need > > it urgently, execute it right now!!! > > > > > yes, and i running every weekend a full analyze, but actually i think > it's > > need again, but just for feel i couldn't stop the server. > > I need evidence. (oldspice rulez ;)) > > > > Szabek > > a plain VACUUM (without full) is enough in most cases... and you don't > need to stop the server for a plain VACUUM... > > -- > regards, > Jaime Casanova > (DBA: DataBase Aniquilator ;) > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > -- "Adopting the position that you are smarter than an automaticoptimization algorithm is generally a good way to achieve lessperformance, not more" - Tom Lane. ------=_Part_29823_13676893.1136482213120 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
http://www.postgresql.org/docs/8.0/interactive/maintenance.html
 
Read all, in order to understand the following quote:
 
"

Since periodic VACUUM runs are needed anyway = for the reasons described earlier, it's unlikely that any table would not b= e vacuumed for as long as a billion transactions. But to help administrator= s ensure this constraint is met,=20 VACUUM stores transaction ID statistics in the s= ystem table pg_database. In particular, the datfrozenxid column of a database's pg_database row is updated at the completion of any database-wide VACUUM operation (i.e., VACUUM= that does not name a specific table). The value stored in this field = is the freeze cutoff XID that was used by that=20 VACUUM command. All normal XIDs older than this = cutoff XID are guaranteed to have been replaced by Fr= ozenXID within that database. A convenient way to examine this informa= tion is to execute the query=20

SELECT datname, age(datfrozenxid) FROM pg=
_database;
"
 
Best wishes,
Guido

 
On 1/5/06, J= aime Casanova <systemguard= s@gmail.com> wrote:
On 1/5/06, Szabolcs BALLA <szballa@confinsystems.com>= ; wrote:
>
>
VACUUM is needed at least every billion transactions...=

execute it in a
> script periodically... if you are in doubt = if you need
VACUUM then you need
> it urgently, execute it right n= ow!!!

>
> yes, and i running every weekend a full analyze, but a= ctually i think it's
> need again, but just for feel i couldn't stop = the server.
> I need evidence. (oldspice rulez ;))
>
> Sz= abek

a plain VACUUM (without full) is enough in most cases... and you do= n't
need to stop the server for a plain VACUUM...

--
regards,<= br>Jaime Casanova
(DBA: DataBase Aniquilator ;)

-----------------= ----------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate      subscribe-nomail command to majordomo@postgresql.org so that your=
      message can get through to the mail= ing list cleanly



--
"Adopting the = position that you are smarter than an automaticoptimization algorithm is ge= nerally a good way to achieve lessperformance, not more" - Tom Lane.= =20 ------=_Part_29823_13676893.1136482213120--