From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Manoel Henrique <mhenriquesgbd(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Research/Implementation of Nested Loop Join optimization |
Date: | 2008-07-26 00:15:48 |
Message-ID: | 20080726001548.GS9891@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake escribió:
> On Fri, 2008-07-25 at 19:31 -0400, Jonah H. Harris wrote:
> > On Fri, Jul 25, 2008 at 6:10 PM, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> > > "Manoel Henrique" <mhenriquesgbd(at)gmail(dot)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
> >
> > :)
>
> What if you are below the equator?
They spin the same direction here too, thanks :-) (Coriolis does not
affect much in this case)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-07-26 00:26:43 | Re: Research/Implementation of Nested Loop Join optimization |
Previous Message | Joshua D. Drake | 2008-07-25 23:35:19 | Re: Research/Implementation of Nested Loop Join optimization |