Received: from k2.aeccom.com (IDENT:root@gate1.aeccom.com [193.158.11.51]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA10848 for ; Fri, 20 Aug 1999 04:13:22 -0400 (EDT) (envelope-from lutzeb@aeccom.com) Received: from blanc.aeccom.com (IDENT:lutzeb@blanc.aeccom.com [192.168.0.10]) by k2.aeccom.com (8.9.3/8.9.3) with ESMTP id KAA12038; Fri, 20 Aug 1999 10:13:20 +0200 Received: (from lutzeb@localhost) by blanc.aeccom.com (8.8.7/8.8.7) id KAA10491; Fri, 20 Aug 1999 10:13:19 +0200 From: Dirk Lutzebaeck MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14269.3615.579004.633506@blanc.aeccom.com> Date: Fri, 20 Aug 1999 10:13:19 +0200 (CEST) To: jwieck@debis.com (Jan Wieck) Cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] does LIMIT save time? In-Reply-To: References: <14268.1018.192099.531387@blanc.aeccom.com> X-Mailer: VM 6.71 under 21.1 (patch 4) "Arches" XEmacs Lucid Jan Wieck writes: > So in general, LIMIT itself could never hurt. ORDER can but > someone who cares for speed is normally willing to setup > appropriate multi key indices to prevent sort steps. Just to know, how can I prevent sorting by using multi key indices? Thanks for your elaborte answer, Dirk