Re: Research/Implementation of Nested Loop Join optimization

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>
Cc: "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-25 23:31:09
Message-ID: 36e682920807251631o48cba2c0y915f0315bd1a6e59@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

:)

--
Jonah H. Harris, Senior DBA
myYearbook.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2008-07-25 23:35:19 Re: Research/Implementation of Nested Loop Join optimization
Previous Message Tom Lane 2008-07-25 23:16:24 Re: pg_dump additional options for performance