Josh Berkus <josh@xxxxxxxxxxxx> writes: > Now, what that says to me is that for this system reverse sequential > reads are 1/4 the speed of forwards reads. And from my testing > elsewhere, that seems fairly typical of disk systems in general. Well, that's because filesystems try to lay out files so that logically successive sectors are about as far apart as needed to support the disk's maximum transfer rate. If you fetch them in reverse order, then instead of optimizing the rotational latency you find you are pessimizing it. This has got approximately nothing to do with indexscans, either forward or reverse, because then we aren't fetching blocks in a pre-optimized order. > Now, while index scans (for indexes on disk) aren't 100% sequential > reads, it seems like we should be increasing (substantially) the > estimated cost of reverse index scans if the index is likely to be on > disk. No? AFAICS this is already folded into random_page_cost. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
