Re: Indexes not always used after inserts/updates/vacuum analyze

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Reinhard Max <max(at)suse(dot)de>
Cc: "Michael G(dot) Martin" <michael(at)vpmonline(dot)com>,pgsql-bugs(at)postgresql(dot)org
Subject: Re: Indexes not always used after inserts/updates/vacuum analyze
Date: 2002-02-28 21:10:21
Message-ID: 14766.1014930621@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs

> Are these the addtional values you wanted to see?

Yes, but I just noticed something else strange:

> -> Index Scan using foo2_pkey on foo2
> (cost=0.00..10387.79 rows=352072 width=4)
> (actual time=0.26..174.32 rows=38432 loops=1)

The actual rows read from this indexscan seem to be many fewer than
the number of rows in the table. What are the ranges of the id values
in tables foo and bar? I'm wondering if the merge could have stopped
far short of the end of the foo table; if so, *that* is the effect that
we are failing to model accurately.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Reinhard Max 2002-03-01 07:06:18 Re: Indexes not always used after inserts/updates/vacuum
Previous Message Steve Wranovsky 2002-02-28 18:52:47 Incorrect PostgreSQL 7.2 ODBC RPM for RedHat 6.2