Re: LIMIT Optimization - Mailing list pgsql-sql

From Bruce Momjian
Subject Re: LIMIT Optimization
Date
Msg-id 200201262311.g0QNBEN00888@candle.pha.pa.us
Whole thread Raw
In response to Re: LIMIT Optimization  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: LIMIT Optimization
List pgsql-sql
Oleg Bartunov wrote:
> On Fri, 25 Jan 2002, Bruce Momjian wrote:
> 
> > > if I'm not mistaken, it's called partial sorting, when you stop
> > > sorting process after getting desired number of rows specified by LIMIT clause.
> > > it's extremely friendly for web applications, because 90% of users
> > > just read the first page of results. We already discussed this feature
> > > sometime during 7.1 dev and even made very crude patch. In our tests we
> > > got performance win of factor 5-6 ( getting first 100 row from 1mln ).
> > > We hope sometime we'll return to this.
> >
> > But we already have cursor's assuming 10% return.  Is allowing that
> > value to be changed using SET an acceptable solution?
> 
> 
> Bruce, web applicationa are stateless, so forget about cursors.
> I wrote about obvious optimization which is valid for very narrow case,
> but which is widely spreaded.

I am confused.  I thought we already did optimization for LIMIT that 
assumed you only wanted a few values.  Is there something we are missing
there?   I thought the disucssion related only to people using cursors
and fetching only some of the data.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: Resources
Next
From: "postgresql"
Date:
Subject: interval and timestamp change?