Karl Wright created CONNECTORS-678:
--------------------------------------

             Summary: Postgresql generating terrible plans for stuffer queries
                 Key: CONNECTORS-678
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-678
             Project: ManifoldCF
          Issue Type: Bug
          Components: Framework core
    Affects Versions: ManifoldCF 1.1.1
            Reporter: Karl Wright
            Assignee: Karl Wright
             Fix For: ManifoldCF 1.2


Query plans like this seem to be taking place:

{code}
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan: Limit  
(cost=9597.49..9597.49 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:   ->  Sort  
(cost=9597.49..9597.49 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:         Sort Key: 
t0.docpriority
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:         ->  Nested Loop 
Anti Join  (cost=17.68..9597.48 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:               Join 
Filter: (t2.jobid <> t0.jobid)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:               ->  
Nested Loop Semi Join  (cost=17.68..9588.87 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                     
Join Filter: (t0.jobid = t1.id)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                     ->  
Nested Loop Anti Join  (cost=17.68..9586.81 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
  Join Filter: (t0.id = t3.owner)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
  ->  Bitmap Heap Scan on jobqueue t0  (cost=4.53..6.54 rows=1 width=155)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        Recheck Cond: (status = ANY ('{P,G}'::bpchar[]))
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        Filter: ((checktime <= 1366628406182::bigint) AND (checkaction = 
'R'::bpchar))
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        ->  Bitmap Index Scan on i1362584563122  (cost=0.00..4.53 rows=1 
width=0)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
              Index Cond: (status = ANY ('{P,G}'::bpchar[]))
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
  ->  Hash Join  (cost=13.15..7635.56 rows=231554 width=8)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        Hash Cond: ((t3.eventname)::text = (t4.name)::text)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        ->  Seq Scan on prereqevents t3  (cost=0.00..4438.54 rows=231554 
width=37)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
        ->  Hash  (cost=11.40..11.40 rows=140 width=516)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
              ->  Seq Scan on events t4  (cost=0.00..11.40 rows=140 width=516)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                     ->  
Seq Scan on jobs t1  (cost=0.00..2.03 rows=2 width=8)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                         
  Filter: ((status = ANY ('{A,a}'::bpchar[])) AND (priority = 5::bigint))
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:               ->  Index 
Scan using i1362584563120 on jobqueue t2  (cost=0.00..4.30 rows=1 width=49)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                     
Index Cond: ((dochash)::text = (t0.dochash)::text)
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) -  Plan:                     
Filter: (status = ANY ('{A,F,a,f,D,d}'::bpchar[]))
 WARN 2013-04-22 13:01:20,414 (Stuffer thread) - 
{code}


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to