From: | Curt Sampson <cjs(at)cynic(dot)net> |
---|---|
To: | mlw <markw(at)mohawksoft(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Index Scans become Seq Scans after VACUUM ANALYSE |
Date: | 2002-04-25 04:12:10 |
Message-ID: | Pine.NEB.4.43.0204251306010.3111-100000@angelic.cynic.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 24 Apr 2002, mlw wrote:
> I am not arguing about whether or not they do it, I am saying it is
> not always possible. I/O requests do not remain in queue waiting for
> reordering indefinitely.
It doesn't matter. When they go out to the disk they go out in
order. On every Unix-based OS I know of, and Novell Netware, if
you submit a single read request for consecutive blocks, those
blocks *will* be read sequentially, no matter what the system load.
So to get back to the original arugment:
> > >The supposed advantage of a sequential read over an random read, in
> > >an active multitasking system, is a myth. If you are executing one
> > >query and the system is doing only that query, you may be right.
No, it's very real, because your sequential read will not be broken up.
If you think it will, let me know which operating systems this
happens on, and how exactly it happens.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-04-25 05:21:16 | md5 passwords and pg_shadow |
Previous Message | Bruce Momjian | 2002-04-25 04:04:24 | Re: Sequential Scan Read-Ahead |