X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5F29D9FA15C for ; Tue, 16 May 2006 15:00:30 -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 23042-09 for ; Tue, 16 May 2006 15:00:22 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.193]) by postgresql.org (Postfix) with ESMTP id 35C0D9F9C9E for ; Tue, 16 May 2006 15:00:21 -0300 (ADT) Received: by wx-out-0102.google.com with SMTP id h31so26142wxd for ; Tue, 16 May 2006 11:00:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=HZgwaeOFYwc/QyPdeHG5LhtUvGmsfigu21KLJ9Pd6+uoYApJZgTZVt9jyfxPhsgsMGzCejMbpO1lW5HKCynjYT1l/bYqquHxg0V5YpxDQliiJKxR814muchTF1MCxd0ePLu+T3O0dwN0UzcWmTCeJMetXIf93BGpifR98dLTZOQ= Received: by 10.70.59.13 with SMTP id h13mr33425wxa; Tue, 16 May 2006 11:00:21 -0700 (PDT) Received: by 10.70.80.16 with HTTP; Tue, 16 May 2006 11:00:21 -0700 (PDT) Message-ID: <1d219a6f0605161100j1a397288y5ed17493542f6f45@mail.gmail.com> Date: Tue, 16 May 2006 14:00:21 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org" Subject: More Autovacuum Questions MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_87036_11570398.1147802421239" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/223 X-Sequence-Number: 21755 ------=_Part_87036_11570398.1147802421239 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks to those who answered my first question. I am looking at implementing autovacuuming on our new production 8.1.3 systems. I am reading the documentation on the various configuration parameters. The autovacuum_analyze_threshold and autovacuum_vacuum_threshold talk about the number of updated and deleted tuples. Is there anyway to calculate these numbers in a running database? The reason I'm asking is that we are having some sporadic slowness issues with our databases, and I'm wanting to see how the database looks during these times. I know that vacuuming some specific tables tends to fix the problem. So, if I can see what autovacuum might see, I could set the parameters correctly to try and fix the issue. Anyway, are these number available to me? Thanks, Chris ------=_Part_87036_11570398.1147802421239 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks to those who answered my first question.  I am looking at imple= menting autovacuuming on our new production 8.1.3 systems.  I am readi= ng the documentation on the various configuration parameters.  The aut= ovacuum_analyze_threshold and autovacuum_vacuum_threshold talk about the nu= mber of updated and deleted tuples.  Is there anyway to calculate thes= e numbers in a running database?

The reason I'm asking is that we are having some sporadic slowness = issues with our databases, and I'm wanting to see how the database looks du= ring these times.  I know that vacuuming some specific tables tends to= fix the problem.  So, if I can see what autovacuum might see, I could= set the parameters correctly to try and fix the issue.

Anyway, are these number available to me?

Thanks,

Chr= is
------=_Part_87036_11570398.1147802421239--