Re: Multiple Order By Criteria - Mailing list pgsql-performance

From J@Planeti.Biz
Subject Re: Multiple Order By Criteria
Date
Msg-id 003201c61bc5$6652d690$81300d05@fatchubby
Whole thread Raw
In response to Multiple Order By Criteria  (J@Planeti.Biz)
Responses Re: Multiple Order By Criteria  ("Ahmad Fajar" <fajar@it-indonesia.info>)
List pgsql-performance
I've read all of this info, closely. I wish when I was searching for an
answer for my problem these pages came up. Oh well.

I am getting an idea of what I need to do to make this work well. I was
wondering if there is more information to read on how to implement this
solution in a more simple way. Much of what's written seems to be towards an
audience that should understand certain things automatically.
----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone.bigpanda.com>
To: <J@planeti.biz>
Cc: "Josh Berkus" <josh@agliodbs.com>; <pgsql-performance@postgresql.org>
Sent: Tuesday, January 17, 2006 6:39 PM
Subject: Re: [PERFORM] Multiple Order By Criteria


>
> On Tue, 17 Jan 2006 J@Planeti.Biz wrote:
>
>> I created the index like this:
>>
>> CREATE INDEX rcbee_idx
>>   ON detail_summary
>>   USING btree
>>   (receipt, carrier_id, batchnum, encounternum, encounter_id);
>>
>> Is this correct ?
>
> That would work if you were asking for all the columns ascending or
> descending, but we don't currently use it for mixed orders.
>
>> How do I make a reverse opclass ?
>
> There's some information at the following:
> http://archives.postgresql.org/pgsql-novice/2005-10/msg00254.php
> http://archives.postgresql.org/pgsql-general/2005-01/msg00121.php
> http://archives.postgresql.org/pgsql-general/2004-06/msg00565.php
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


pgsql-performance by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Multiple Order By Criteria
Next
From: Mark Kirkwood
Date:
Subject: Re: Suspending SELECTs