X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 79985D1B4BA for ; Mon, 8 Dec 2003 15:36:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 35649-09 for ; Mon, 8 Dec 2003 11:35:50 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 3E177D1B481 for ; Mon, 8 Dec 2003 11:35:46 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hB8FZn19009619; Mon, 8 Dec 2003 10:35:50 -0500 (EST) To: swampler@noao.edu Cc: Robert Treat , Postgres-performance Subject: Re: Help tracking down problem with inserts slowing In-reply-to: <1070896493.20063.159.camel@weaver.tuc.noao.edu> References: <1070661108.20063.86.camel@weaver.tuc.noao.edu> <200312052154.52223.xzilla@users.sourceforge.net> <20031207142816.GA8321@weaver.tuc.noao.edu> <20031207145235.GA8734@weaver.tuc.noao.edu> <22388.1070815957@sss.pgh.pa.us> <1070896493.20063.159.camel@weaver.tuc.noao.edu> Comments: In-reply-to Steve Wampler message dated "Mon, 08 Dec 2003 08:14:53 -0700" Date: Mon, 08 Dec 2003 10:35:49 -0500 Message-ID: <9618.1070897749@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/153 X-Sequence-Number: 5013 Steve Wampler writes: > Thanks, Tom. Are there any reasons why it would not appear?: Oh, I shoulda read the code more carefully. I was looking at the bottom of lazy_scan_index, where the printout is done, and failed to notice the test at the top: /* * If the index is not partial, skip the scan, and just assume it has * the same number of tuples as the heap. */ So for ordinary indexes, nothing will appear unless vacuum has actual work to do (that is, it recycled at least one dead tuple in the table). Short answer: update or delete some row in the table, and then try vacuum verbose. Alternatively, you can just look at the pg_class row for the index. relpages and reltuples will contain the info you are after ... and they are certainly up to date at this point ;-) regards, tom lane