pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dirk Lutzebaeck <lutzeb@aeccom.com>
To: jwieck@debis.com
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] does LIMIT save time?
Date: Fri, 20 Aug 1999 10:13:19 +0200 (CEST)
Message-ID: <14269.3615.579004.633506@blanc.aeccom.com> (raw)
In-Reply-To: <m11HZfN-0003kLC@orion.SAPserv.Hamburg.dsh.de>
References: <14268.1018.192099.531387@blanc.aeccom.com>
	<m11HZfN-0003kLC@orion.SAPserv.Hamburg.dsh.de>

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



view thread (3+ messages)

Message-ID: <14269.3615.579004.633506@blanc.aeccom.com>
Permalink:  ../14269.3615.579004.633506@blanc.aeccom.com/
Also on:    postgresql.org/message-id/14269.3615.579004.633506@blanc.aeccom.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: lutzeb@aeccom.com, jwieck@debis.com
  Subject: Re: [SQL] does LIMIT save time?
  In-Reply-To: <14269.3615.579004.633506@blanc.aeccom.com>
  References: <14268.1018.192099.531387@blanc.aeccom.com> <m11HZfN-0003kLC@orion.SAPserv.Hamburg.dsh.de> <14269.3615.579004.633506@blanc.aeccom.com>

* 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