pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew Hagerty <matthew@venux.net>
To: pgsql-interfaces@postgreSQL.org
Subject: LIMIT and 6.5
Date: Fri, 04 Jun 1999 22:55:00 -0400
Message-ID: <4.1.19990604224611.00a838e0@mail.venux.net> (raw)

Greetings,

I was wondering if the new LIMIT command in 6.5 is implemented in such a
way that it does in fact improve query time and memory on large result
sets?  I was reading a patch that gives the LIMIT command capability to
6.4.2, but there was a note that indicated that the query processor still
had to evaluate the whole query and only *returns* the indicated number of
tuples/rows.  Is that the case with 6.5 also?  If so, what is the use of
having such a command if it does not improve performance or save memory?
It is already possible (and easy) to just grab x number of tuples/rows from
a query since most of the time they are fetched in a loop anyway.

Thanks,
Matthew Hagerty




Message-ID: <4.1.19990604224611.00a838e0@mail.venux.net>
Permalink:  ../4.1.19990604224611.00a838e0@mail.venux.net/
Also on:    postgresql.org/message-id/4.1.19990604224611.00a838e0@mail.venux.net

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: matthew@venux.net
  Subject: Re: LIMIT and 6.5
  In-Reply-To: <4.1.19990604224611.00a838e0@mail.venux.net>

* 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