Thread

  1. Query Planning time increased 3 times on 7.1 compared to 7.0.3

    Christof Petig <christof@petig-baender.de> — 2001-03-03T11:30:58Z

    Hello,
    
    We noticed that after upgrading to 7.1beta[245] the execution time for
    some often used queries went up by a factor of 2 or more. Considering
    the early beta state I was not alarmed. But since I noticed that
    yesterday's snapshot still has the problem, I'd really like to tell you
    about it.
    
    Here is one of the queries, it takes about half a second on our computer
    (PII 233 with 256MB RAM) to execute and returns typically 1-4 rows via
    two index scans with high selectivity. So it looks to me that planning
    time outwages execution time by far. 7.0 took about 0.15 seconds (which
    is still much).
    
    Here is the query:
    
    explain verbose select  gaenge  , s . artikelid  , text   from
    schaertabelle s , extartbez e where maschine  = int2(109) and
    schaerdatum  = '2001-01-13' and s . artikelid  = e . artikelid  and
    extartbezid  = 1 and bezkomptype  = 0   order by text    limit 10;
    
    And the plan for 7.0 and 7.1 (attached).
    
    The data and schema is accessible via
    http://home.wtal.de/petig/pg_test.sql.gz
    
    If you omit 'int2(' the index scan collapses into a sequential scan.
    (Well known problem with int2 indices)
    
       Christof
    
    Oh, I'll attach the schema, too. So if you just want to take a look at
    the table definition you don't have to download the data.