Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA24636 for ; Fri, 14 Jan 2000 11:52:48 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA01122; Fri, 14 Jan 2000 11:37:19 -0500 (EST) From: Bruce Momjian Message-Id: <200001141637.LAA01122@candle.pha.pa.us> Subject: Re: [SQL] Optimizing ORDER BY with indexes? In-Reply-To: <14462.60668.225811.469623@ampato.aeccom.com> from Dirk Lutzebaeck at "Jan 14, 2000 10:31:40 am" To: Dirk Lutzebaeck Date: Fri, 14 Jan 2000 11:37:19 -0500 (EST) CC: pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Dirk Lutzebaeck writes: > > > > I'm forced to used ORDER BY on large tables which then takes quite > > long. Is there a chance to create/optimize an index for ORDER BY? > > Or could I write an index method on my own? How would it look like? > > > > Are there any other possiblities to speed up ORDER BY? > > Reading about indexes in the Bowman SQL book I think a > _clustered index_ is needed for the problem above. > Does Postgresql support these? > CLUSTER command. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026