Re: Why won't it index scan?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Why won't it index scan?
Date: 2006-05-23 22:18:07
Message-ID: 23611.1148422687@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Mon, May 22, 2006 at 06:43:22PM -0400, Tom Lane wrote:
>> It would be nice to have some *evidence*, not unsupported handwaving.

> If someone has an idea on how to actually get that evidence, I'm all
> ears.

Well, for example, actually measuring the planner overhead from larger
pg_statistic entries would be interesting. Plus how much more time
ANALYZE takes to generate the entries. (I'm afraid that ANALYZE is
probably worse-than-linear CPU-wise, but it may be dominated by disk
access.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-23 22:19:58 Re: allow LIMIT in UPDATE and DELETE
Previous Message Joshua D. Drake 2006-05-23 22:17:41 Re: Why won't it index scan?