From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Steve Wolfe <steve(at)iboats(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Performance question (stripped down the problem) |
Date: | 2001-09-27 23:20:27 |
Message-ID: | 20010928092027.A32426@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Sep 27, 2001 at 11:18:31AM -0600, Steve Wolfe wrote:
> This is interesting, just yesterday I was perusing some of Bruce
> Momjian's works on PG tuning, and noticed that Postgres prefers sequential
> scans over indexes when much of the table has to be read, all because of
> the number of head movements on the disk. It would seem that these days,
> where RAM is cheap, that most people have a great enough disk cache that
> head movements can become irrelevant.
>
> However, I can also see where some people may have incredibly large
> tables that just won't fit into RAM. An easy solution to both might be to
> create a user-specifiable switch passed at startup that would simply tell
> PG that sequentials aren't necessarily better than index scans. Not
> completely disabling them, but at least giving it a pointer that it
> doesn't *have* to use sequentials.
There is a user specifieable value somewhere that controls how expensive an
index scan is and how expensive a seqential scan is. By tuning those you
could probably get the effect you want.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org>
http://svana.org/kleptog/
> Magnetism, electricity and motion are like a three-for-two special offer:
> if you have two of them, the third one comes free.
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2001-09-27 23:23:14 | Re: How to make a REALLY FAST db server? |
Previous Message | Bruce Momjian | 2001-09-27 23:15:58 | Re: Encoding passwords |