Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 543B164FCCB for ; Fri, 31 Oct 2008 12:32:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 69336-02 for ; Fri, 31 Oct 2008 12:32:47 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by postgresql.org (Postfix) with ESMTP id A0A4164FC6F for ; Fri, 31 Oct 2008 12:32:46 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k40so1312597ugc.7 for ; Fri, 31 Oct 2008 08:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=T3vI75KZ9KMigino1Zws+59PPkHE69NtBRtOrERe7Sc=; b=la86KTNUhbpUfk6l5oAHn24TLF16rK+nHwWIJ22uReJBUygX8R4SMkB+y+hReRTEBo B9pY7Jl3+H6H3R2k942LOVfTRlPuLkuhK0jcqBXsg67mgW6hIemSi2ERaWiMq9FelBSD FXC42HQxsdKGdN3yHgHeunMgBz3ZU+gleoR+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=j5WfQN1/uB/UbS1qA6Y+/m4oJf9+ESjE1rdf2r7FtMyVNX1tQqexeUbML6wb7scAxh yG1FbPmucwZLUIetBCnDDQYeNcGCjls6ZsWMWvJIMunQtUhro64OG8UevY0IrUx5w/Ca X5iRy7SrAh1iPI2BpNmLcjjVXIYqe7MqcIZmE= Received: by 10.86.99.9 with SMTP id w9mr8489943fgb.38.1225467165325; Fri, 31 Oct 2008 08:32:45 -0700 (PDT) Received: by 10.86.86.10 with HTTP; Fri, 31 Oct 2008 08:32:45 -0700 (PDT) Message-ID: <3a0028490810310832t2972fb95l6c8d01e7895c1b6c@mail.gmail.com> Date: Fri, 31 Oct 2008 14:32:45 -0100 From: "Rafael Domiciano" To: isabella.ghiurea@nrc-cnrc.gc.ca Subject: Re: autovacuum questions Cc: pgsql-admin@postgresql.org In-Reply-To: <490B2161.1070502@nrc-cnrc.gc.ca> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29064_23999381.1225467165303" References: <490B2161.1070502@nrc-cnrc.gc.ca> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200810/195 X-Sequence-Number: 30651 ------=_Part_29064_23999381.1225467165303 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello there, Yes, the autovacuum is set on by default on the PG 8.3. The vacuum is not full, to run a full vacuum you need to set a cron job; better to run at the night. I don't set autovacuum on the production databases, only in the Slony's slave machines and in the developmente machine. For autovacuum settings you need to set and see if it's ok for you. to see if the vacuum is running you can use the command "ps axf | grep postgres" on the linux server. Sometimes autovacuum is so fast that you even notice him. I hope that I helped Best Regards, Rafael Domiciano 2008/10/31 Isabella Ghiurea > Hello Gurus, > I'm new to PG , running PG 8.3 on Linux and reading trough docs is > mentioned that in PG vers 8.3 an AUTO vacuum process has been implemented > which will run > full vacuum on all user and system tables + analyze and there is NO > need fro DBA to schedule a crontab job to run this maintenance jobs . If > this is true , here are my questions : > Would like to know from your experience is this automated process > sufficient and reliable in a warehouse database , can I rely only on this > internal process ? > How can I see when the job has been run or completed by PG ? > I have configure track_count=true, what values should I go for > autovacuum_naptime from your experience? > > Isabella > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > ------=_Part_29064_23999381.1225467165303 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hello there,

Yes, the autovacuum is set on by default on the PG 8.3.
The vacuum is not full, to run a full vacuum you need to set a cron job; better to run at the night.
I don't set autovacuum on the production databases, only in the Slony's slave machines and in the developmente machine.
For autovacuum settings you need to set and see if it's ok for you.
to see if the vacuum is running you can use the command "ps axf | grep postgres" on the linux server. Sometimes autovacuum is so fast that you even notice him.

I hope that I helped

Best Regards,

Rafael Domiciano

2008/10/31 Isabella Ghiurea <isabella.ghiurea@nrc-cnrc.gc.ca>
Hello Gurus,
I'm new to PG , running PG 8.3 on Linux and reading trough docs  is mentioned that in PG vers 8.3  an AUTO vacuum process   has been implemented which will run
full vacuum  on  all user and system tables + analyze  and there is  NO need fro DBA  to schedule a crontab job to run this  maintenance jobs . If this is true , here are my questions :
Would like to know from your experience is this automated process sufficient and reliable in a warehouse database , can I rely only  on this  internal  process ?
How can I see when the job has been run or completed by PG ?
I have configure track_count=true, what values should I go for autovacuum_naptime  from your experience?

Isabella


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

------=_Part_29064_23999381.1225467165303--