Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.2/8.9.1) with SMTP id HAA93516 for ; Thu, 11 Feb 1999 07:15:13 -0500 (EST) (envelope-from wieck@sapserv.debis.de) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m10Av7m-000EBRC; Thu, 11 Feb 99 13:21 MET Message-Id: From: jwieck@debis.com (Jan Wieck) Subject: Re: [SQL] setting select limit? To: maillist@remo.demon.co.uk (Neil Burrows) Date: Thu, 11 Feb 1999 13:21:41 +0100 (MET) Cc: oleg@sai.msu.su, pgsql-sql@postgreSQL.org Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: <000901be55a8$1bea7710$c6cb9284@towhee.gssec.bt.co.uk> from "Neil Burrows" at Feb 11, 99 10:20:12 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > Hi, > > > You need v6.4.2-feature-patch which implement LIMIT option: > > Or alternatively if you can't or don't want to apply a patch, have a look at > the > > SET QUERY_LIMIT TO x > > in Postgres 6.4 It is commented out by default (#ifdef QUERY_LIMIT) and I recommend NOT to enable it. The implementation of SET QUERY_LIMIT hat unwanted side effects. If during the execution of such a query functions or triggers get invoked, the query limit also affects the execution of their queries. That could damage triggers or give unpredictable results on functions. I'll ensure that the SET QUERY_LIMIT code will be removed in v6.5. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #