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 14:51:06
Message-ID: 13022.1014907866@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Reinhard Max <max(at)suse(dot)de> writes:
> I've just found a case where forcing indexscans results in much higher
> speed.

> -> Index Scan using foo_pkey on foo
> (cost=0.00..25153.18 rows=352072 width=4)
> (actual time=0.03..157.57 rows=38432 loops=1)

The major estimation error is evidently in this indexscan. What
statistics does pg_stats show for this table?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Reinhard Max 2002-02-28 15:00:47 Re: Indexes not always used after inserts/updates/vacuum
Previous Message Michael G. Martin 2002-02-28 14:40:15 Re: Indexes not always used after inserts/updates/vacuum analyze