Re: [PERFORM] Select running slow on Postgres

2008-07-02 Thread Scott Marlowe
On Wed, Jul 2, 2008 at 1:01 PM, samantha mahindrakar <[EMAIL PROTECTED]> wrote: > I ran the explain analyze.Here is what i got: > > > "Group (cost=112266.37..112266.40 rows=1 width=56) (actual > time=5583.399..5615.476 rows=13373 loops=1)" > " -> Sort (cost=112266.37..112266.38 rows=1 width=56)

Re: [PERFORM] Select running slow on Postgres

2008-07-02 Thread samantha mahindrakar
I ran the explain analyze.Here is what i got: "Group (cost=112266.37..112266.40 rows=1 width=56) (actual time=5583.399..5615.476 rows=13373 loops=1)" " -> Sort (cost=112266.37..112266.38 rows=1 width=56) (actual time=5583.382..5590.890 rows=13373 loops=1)" "Sort Key: lane_data_07_08.l

Re: [PERFORM] Select running slow on Postgres

2008-07-01 Thread Scott Marlowe
On Tue, Jul 1, 2008 at 1:29 PM, samantha mahindrakar <[EMAIL PROTECTED]> wrote: > Hi > I have a select statement that runs on a partition having say couple > million rows. > The tabel has indexes on two colums. However the query uses the > non-indexed colums too in its where clause. > For example:

[PERFORM] Select running slow on Postgres

2008-07-01 Thread samantha mahindrakar
Hi I have a select statement that runs on a partition having say couple million rows. The tabel has indexes on two colums. However the query uses the non-indexed colums too in its where clause. For example: SELECT lane_id,measurement_start, measurement_end,speed,volume,occupancy,quality,effective_d