pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: swampler@noao.edu
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: Postgres-performance <pgsql-performance@postgresql.org>
Subject: Re: Help tracking down problem with inserts slowing
Date: Mon, 08 Dec 2003 10:35:49 -0500
Message-ID: <9618.1070897749@sss.pgh.pa.us> (raw)
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>

Steve Wampler <swampler@noao.edu> 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



view thread (9+ messages)

Message-ID: <9618.1070897749@sss.pgh.pa.us>
Permalink:  ../9618.1070897749@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/9618.1070897749@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, swampler@noao.edu, xzilla@users.sourceforge.net
  Subject: Re: Help tracking down problem with inserts slowing
  In-Reply-To: <9618.1070897749@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox