X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 4C0BB9F9998 for ; Tue, 20 Jun 2006 17:49:43 -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 07035-10 for ; Tue, 20 Jun 2006 17:49:31 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.198]) by postgresql.org (Postfix) with ESMTP id 67F759FA682 for ; Tue, 20 Jun 2006 17:49:26 -0300 (ADT) Received: by wx-out-0102.google.com with SMTP id s15so863wxc for ; Tue, 20 Jun 2006 13:49:25 -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=Vdh/26fHla2AHsvDz/kF/5tqvJFkRzGgBxn53xyJgawafUgdMYEYjJsMNOacqxPoFlIzWVRxsjPqtmbbmFXUjW8p8X1fkQAALlvqcPFQ6kzjagqI+7GQ1E65mBy3mHBrHjnSXDhMg0XKLBAwAmJcaMgwcEQ4bw9QezJ45v1EBSo= Received: by 10.70.103.15 with SMTP id a15mr11018961wxc; Tue, 20 Jun 2006 13:49:25 -0700 (PDT) Received: by 10.70.73.15 with HTTP; Tue, 20 Jun 2006 13:49:25 -0700 (PDT) Message-ID: <1d219a6f0606201349w48f2cfd0s68914352c76cb4a0@mail.gmail.com> Date: Tue, 20 Jun 2006 16:49:25 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org" Subject: Question on vacuum output MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29442_32556949.1150836565347" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/165 X-Sequence-Number: 22127 ------=_Part_29442_32556949.1150836565347 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I am having some performance issues on some of my larger databases (50-100+GB). I just ran a vacuum analyze on our key table, and saw this at the end. DETAIL: 562499 dead row versions cannot be removed yet. There were 15117 unused item pointers. 0 pages are entirely empty. CPU 8.32s/2.59u sec elapsed 340.19 sec. INFO: analyzing "public.clmhdr" INFO: "clmhdr": scanned 30000 of 221695 pages, containing 259684 live rows and 75400 dead rows; 30000 rows in sample, 1919021 estimated total rows VACUUM What does this mean that there are 562499 dead row versions that could not be removed? Could this be part of the performance issue? I have a query that before the vacuum was running in 1-2 seconds and normally after a vacuum analyze will run in a couple hundred miliseconds. (Although this run of the vacuum analyze does not appear to have helped much, my tell tale query is still running 1sec+). Thanks, Chris ------=_Part_29442_32556949.1150836565347 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am having some performance issues on some of my larger databases (50-100+GB).  I just ran a vacuum analyze on our key table, and saw this at the end.

DETAIL:  562499 dead row versions cannot be removed yet.
There were 15117 unused item pointers.
0 pages are entirely empty.
CPU 8.32s/2.59u sec elapsed 340.19 sec.
INFO:  analyzing "public.clmhdr"
INFO:  "clmhdr": scanned 30000 of 221695 pages, containing 259684 live rows and 75400 dead rows; 30000 rows in sample, 1919021 estimated total rows
VACUUM


What does this mean that there are 562499 dead row versions that could not be removed?  Could this be part of the performance issue?  I have a query that before the vacuum was running in 1-2 seconds and normally after a vacuum analyze will run in a couple hundred miliseconds.  (Although this run of the vacuum analyze does not appear to have helped much, my tell tale query is still running 1sec+).

Thanks,

Chris
------=_Part_29442_32556949.1150836565347--