Re: cannot use multicolumn index - Mailing list pgsql-performance

From MirrorX
Subject Re: cannot use multicolumn index
Date
Msg-id 1316005753084-4802699.post@n5.nabble.com
Whole thread Raw
Responses Re: cannot use multicolumn index
Re: cannot use multicolumn index
List pgsql-performance
here is the explain analyze output->
server=# explain analyze select count(*) from temp_by_hour where xid > 100
and xdate > now() - interval '1 week';
                                                                    QUERY
PLAN

---------------------------------------------------------------------------------------------------------------------------------------------------
 Aggregate  (cost=29359311.58..29359311.59 rows=1 width=0) (actual
time=2728061.589..2728061.590 rows=1 loops=1)
   ->  Seq Scan on temp_by_hour (cost=0.00..29345234.14 rows=5630975
width=0) (actual time=560446.661..2726838.501 rows=5760724 loops=1)
         Filter: ((xid > 100) AND (xdate > (now() - '7 days'::interval)))
 Total runtime: 2728063.170 ms

--
View this message in context:
http://postgresql.1045698.n5.nabble.com/cannot-use-multicolumn-index-tp4802634p4802699.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

pgsql-performance by date:

Previous
From: Leonardo Francalanci
Date:
Subject: Re: Hash index use presently(?) discouraged since 2005: revive or bury it?
Next
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: cannot use multicolumn index