Re: Yet another slow nested loop

From: Alexander Staubo <alex(at)bengler(dot)no>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Yet another slow nested loop
Date: 2009-06-16 15:16:35
Message-ID: 88daf38c0906160816w78a34c0dwd7741e7d8236242e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Jun 16, 2009 at 4:36 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Actually the easiest way to fix that is to get rid of the LIMIT.
> (Maybe use a cursor instead, and fetch only twenty rows.)  LIMIT
> magnifies the risks from any estimation error, and you've got a lot
> of that here ...

There's no cursor support in ActiveRecord, the ORM library we use, and
I'm not going to write it. Anyway, I would prefer not to gloss over
the underlying problem with something that requires a "TODO" next to
it. What can be done to fix the underlying problem? Nothing?

A.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2009-06-16 15:31:30 Re: performance with query
Previous Message Alberto Dalmaso 2009-06-16 15:12:54 Re: performance with query