Re: Why won't it index scan?

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

On Tuesday May 23 2006 4:55 pm, Jim C. Nasby wrote:
> Well, I did find one reason not to go ape with this: the
> number of pages analyzed scales with the number of buckets, so
> doubling the statistics target will roughly double the ANALYZE
> time for any table over 6000 pages (though the effect isn't
> linear, see below). There is a small increase in time for a
> small table, but I doubt it's enough for anyone to care:

Are you accounting for your well-primed OS and DB caches? I'd
think a more realistic test would clear those of the target
table between measurements.

Ed

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-23 23:11:28 Re: [GENERAL] Debugging SQL queries
Previous Message Tom Lane 2006-05-23 22:59:49 Re: assymetry updating a boolean (=FALSE faster than =TRUE)