Re: [PERFORM] Multiple Order By Criteria

2006-01-18 Thread J
OTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 18, 2006 2:24 PM Subject: Re: [PERFORM] Multiple Order By Criteria On Wed, 18 Jan 2006 [EMAIL PROTECTED] wrote: Could you explain to me how do create this operator class for a text data type ? I think it will give me more

Re: [PERFORM] Multiple Order By Criteria

2006-01-18 Thread Stephan Szabo
On Wed, 18 Jan 2006 [EMAIL PROTECTED] wrote: > I have the answer I've been looking for and I'd like to share with all. > After help from you guys, it appeared that the real issue was using an index > for my order by X DESC clauses. For some reason that doesn't make good > sense, postgres doesn't s

Re: [PERFORM] Multiple Order By Criteria

2006-01-18 Thread J
I have the answer I've been looking for and I'd like to share with all. After help from you guys, it appeared that the real issue was using an index for my order by X DESC clauses. For some reason that doesn't make good sense, postgres doesn't support this, when it kinda should automatically.

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread Ahmad Fajar
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Rabu, 18 Januari 2006 07:23 To: Stephan Szabo Cc: Josh Berkus; pgsql-performance@postgresql.org Subject: Re: [PERFORM] Multiple Order By Criteria I've read all of this info, cl

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread J
06 6:39 PM Subject: Re: [PERFORM] Multiple Order By Criteria On Tue, 17 Jan 2006 [EMAIL PROTECTED] 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 w

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread Stephan Szabo
On Tue, 17 Jan 2006 [EMAIL PROTECTED] 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 o

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread J
To: "Josh Berkus" Cc: ; <[EMAIL PROTECTED]> Sent: Tuesday, January 17, 2006 5:40 PM Subject: Re: [PERFORM] Multiple Order By Criteria On Tue, 17 Jan 2006, Josh Berkus wrote: J, > I have an index built for each of these columns in my order by clause. > This query takes an

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread Fredrick O Jackson
scan and > not use my super new index. > > Am I doing something wrong ? > > - Original Message - > From: "Josh Berkus" > To: > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, January 17, 2006 5:25 PM > Subject: Re: [PERFORM] Multiple Order By Criteria

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread Stephan Szabo
On Tue, 17 Jan 2006, Josh Berkus wrote: > J, > > > I have an index built for each of these columns in my order by clause. > > This query takes an unacceptable amount of time to execute. Here are the > > results of the explain: > > You need a single index which has all five columns, in order. I t

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread J
new index. Am I doing something wrong ? - Original Message - From: "Josh Berkus" To: Cc: <[EMAIL PROTECTED]> Sent: Tuesday, January 17, 2006 5:25 PM Subject: Re: [PERFORM] Multiple Order By Criteria J, I have an index built for each of these columns in my order by clause.

Re: [PERFORM] Multiple Order By Criteria

2006-01-17 Thread Josh Berkus
J, > I have an index built for each of these columns in my order by clause. > This query takes an unacceptable amount of time to execute. Here are the > results of the explain: You need a single index which has all five columns, in order. -- --Josh Josh Berkus Aglio Database Solutions San Fran

[PERFORM] Multiple Order By Criteria

2006-01-17 Thread J
I'm trying to query a table with 250,000+ rows. My query requires I provide 5 colums in my "order by" clause:   select   column from table where  column >= '2004-3-22 0:0:0'order by     ds.receipt desc,     ds.carrier_id asc,     ds.batchnum asc,     encounternum asc,     ds.encounter_id AS