Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA65647 for ; Fri, 4 Jun 1999 22:54:32 -0400 (EDT) (envelope-from matthew@venux.net) Received: from thunder (net177138.hcv.com [209.153.177.138]) by redbox.venux.net (Postfix) with SMTP for id 580002E20E; Fri, 4 Jun 1999 22:52:24 -0400 (EDT) Message-Id: <4.1.19990604224611.00a838e0@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 04 Jun 1999 22:55:00 -0400 To: pgsql-interfaces@postgreSQL.org From: Matthew Hagerty Subject: LIMIT and 6.5 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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