pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Moray McConnachie <moray.mcconnachie@computing-services.oxford.ac.uk>
Cc: tjk@tksoft.com, "Roderick A. Anderson" <raanders@altoplanos.net>
Cc: oleg@sai.msu.su
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] trivial problem
Date: Fri, 29 Oct 1999 16:19:57 -0400 (EDT)
Message-ID: <199910292019.QAA07363@candle.pha.pa.us> (raw)
In-Reply-To: <003101bf2248$76e0d8e0$9f1b4cc0@public.ox.ac.uk>

FAQ says:

See the <I>fetch</I> manual page, or use SELECT ... LIMIT....<P>

This only prevents all row results from being transferred to the client.
The entire query must be evaluated, even if you only want just the first
few rows. Consider a query that has an <I>order by.</I>  There is no way
to return any rows until the entire query is evaluated and sorted.<P>

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> 
> ----- Original Message -----
> From: <tjk@tksoft.com>
> To: Roderick A. Anderson <raanders@altoplanos.net>
> Cc: <oleg@sai.msu.su>; <pgsql-sql@postgreSQL.org>
> Sent: Friday, October 29, 1999 7:12 PM
> Subject: Re: [SQL] trivial problem
> 
> 
> > If limit didn't mean "get first 50," there would be no time/effort
> > saved by specifying a limit.
> >
> > I.e. when a limit is specified, the backend looks for matches until it
> > finds 50 records, and then stops.
> 
> Eh? I think the questioner meant effectively "in a query with LIMIT and
> ORDER BY, which takes precedence?". To which the answer appears  to be ORDER
> BY, which surprised me, but is of course very useful.
> 
> I.e. all sorting is completed, and then the first fifty records are
> returned.
> 
> Does that mean that the seek time for a limited, ordered by query is the
> same as that for an unlimited query? The extra speed gained from the limit
> only achieved by not having to return the data? Or is there some kind of
> magic going on to allow it to ignore certain things about the query when a
> LIMIT is in place?
> 
> 
> ************
> 
> 


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



view thread (9+ messages)  latest in thread

Message-ID: <199910292019.QAA07363@candle.pha.pa.us>
Permalink:  ../199910292019.QAA07363@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199910292019.QAA07363@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: maillist@candle.pha.pa.us, moray.mcconnachie@computing-services.oxford.ac.uk, raanders@altoplanos.net, oleg@sai.msu.su
  Subject: Re: [SQL] trivial problem
  In-Reply-To: <199910292019.QAA07363@candle.pha.pa.us>
  References: <003101bf2248$76e0d8e0$9f1b4cc0@public.ox.ac.uk> <199910292019.QAA07363@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox