Re: Why won't it index scan?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 00:55:16
Message-ID: 44725D74.7060008@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> The reason the default is currently 10 is just conservatism: it was
> already an order of magnitude better than what it replaced (a *single*
> representative value) and I didn't feel I had the evidence to justify
> higher values. It's become clear that the default ought to be higher,
> but I've still got no good fix on a more reasonable default. 100 might
> be too much, or then again maybe not.
>

My hands on experience is that 10 is plenty except for the minority of
tables within a database. Those table can be accurately represented
using alter table without having to adjust the global.

That being said, 10 is fairly small and I often find myself setting the
value to at least 250 just to keep it out of my way.

Sincerely,

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Reyes 2006-05-23 02:17:12 Re: psql freezes loading large file
Previous Message Tom Lane 2006-05-23 00:30:20 Re: psql freezes loading large file