From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | "Ed L(dot)" <pgsql-general(at)bluepolka(dot)net> |
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:35:50 |
Message-ID: | 20060523233550.GQ64371@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 23, 2006 at 05:00:13PM -0600, Ed L. wrote:
> 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.
That was after a number of other analyze runs that had already happened,
and the table way larger than my cache, so it's unlikely that caching
played much of an issue.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Shelby Cain | 2006-05-24 00:29:14 | Re: allow LIMIT in UPDATE and DELETE |
Previous Message | Jim C. Nasby | 2006-05-23 23:26:09 | Re: [SQL] (Ab)Using schemas and inheritance |