Re: [PERFORM] Problems with ordering (can't force query planner to use an index)

2009-03-03 Thread Sebastjan Trepca
loops=1) Filter: ((publish_state >= 60) AND (slot_type_id = 119) AND (slot_id = 472) AND (label = ''::text) AND (role = 0) AND (user_id = 0)) Total runtime: 4597.632 ms (4 rows) Sebastjan On Tue, Mar 3, 2009 at 8:05 PM, Sebastjan Trepca wrote: > Still the same :/ &

Re: [PERFORM] Problems with ordering (can't force query planner to use an index)

2009-03-03 Thread Sebastjan Trepca
6:40 PM, Robert Haas wrote: > On Tue, Mar 3, 2009 at 12:20 PM, Sebastjan Trepca wrote: >> But it's already attached in the first mail or am I missing something? >> >> If you don't see it, check this: http://pastebin.com/d71b996d0 > > Woops, sorry, I thought you ha

Re: [PERFORM] Problems with ordering (can't force query planner to use an index)

2009-03-03 Thread Sebastjan Trepca
e=0.058..55.225 rows=69312 loops=1) Index Cond: ((slot_id = 472) AND (slot_type_id = 119) AND (label = ''::text) AND (user_id = 0) AND (role = 0) AND (publish_state >= 60)) -> Index Scan using core_base_pkey on core_base (cost=0.00..8.92 rows=1 width=768

Re: [PERFORM] Problems with ordering (can't force query planner to use an index)

2009-03-03 Thread Sebastjan Trepca
But it's already attached in the first mail or am I missing something? If you don't see it, check this: http://pastebin.com/d71b996d0 Sebastjan On Tue, Mar 3, 2009 at 6:12 PM, Robert Haas wrote: > On Tue, Mar 3, 2009 at 12:05 PM, Sebastjan Trepca wrote: >> Hey, >&g

[PERFORM] Problems with ordering (can't force query planner to use an index)

2009-03-03 Thread Sebastjan Trepca
Hey, I have a table that links content together and it currently holds about 17 mio records. Typical query is a join with a content table and link table: noovo-new=# explain analyze SELECT "core_accessor"."id", "core_accessor"."content_type_id", "core_accessor"."object_id", "core_accessor"."order