Re: Research/Implementation of Nested Loop Join optimization - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Research/Implementation of Nested Loop Join optimization
Date
Msg-id 20080726003725.GT9891@alvh.no-ip.org
Whole thread Raw
In response to Re: Research/Implementation of Nested Loop Join optimization  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Research/Implementation of Nested Loop Join optimization  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane escribió:
> Gregory Stark <stark@enterprisedb.com> writes:
> > "Manoel Henrique" <mhenriquesgbd@gmail.com> writes:
> >> Yes, I'm relying on the assumption that backwards scan has the same cost as
> >> forward scan, why shouldn't it?
> 
> > Because hard drives only spin one direction
> 
> Good joke, but to be serious: we expect that forward scans will result
> in the kernel doing read-ahead, which will allow overlapping of
> CPU work to process one page with the I/O to bring in the next page.

I wonder if this is spoiled (or rather, the backwards case fixed) by the
attempts to call posix_fadvise() on certain types of scan.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: daveg
Date:
Subject: Re: Adding WHERE clause to pg_dump
Next
From: Tom Lane
Date:
Subject: Re: Research/Implementation of Nested Loop Join optimization