Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id A3FF9475AAF for ; Sat, 18 May 2002 19:03:49 -0400 (EDT) Received: from conan.partner2partner.org (unknown [65.160.7.101]) by postgresql.org (Postfix) with SMTP id B6AB4475987 for ; Sat, 18 May 2002 19:03:48 -0400 (EDT) Received: (qmail 22058 invoked by uid 89); 18 May 2002 23:18:14 -0000 Message-ID: <20020518231814.22057.qmail@conan.partner2partner.org> References: <1021760653.30045.296.camel@kant.mcmillan.net.nz> In-Reply-To: <1021760653.30045.296.camel@kant.mcmillan.net.nz> From: "mike" To: Postgres-PHP Subject: Re: using CURSOR with PHP Date: Sat, 18 May 2002 23:18:14 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Archive-Number: 200205/66 X-Sequence-Number: 1198 Andrew McMillan writes: > PostgreSQL will certainly take LIMIT into account when planning queries. I would think most queries using LIMIT would also include an ORDER BY clause which would require PostgreSQL to sort all the results before applying the LIMIT. > OTOH PostgreSQL does _not_ do result caching, unless you have applied > some patches that were floating around last year some time. PostgreSQL might not do 'result caching' but if you have an adequate number of buffers configured would it not be likely that the results from the last query are still in memory? Michael J. Upchurch Partner2Partner Communications mike@partner2partner.com 615.286.2199