• Tom Lane's avatar
    Avoid unexpected slowdown in vacuum regression test. · 5b3ce2c9
    Tom Lane authored
    I noticed the "vacuum" regression test taking really significantly longer
    than it used to on a slow machine.  Investigation pointed the finger at
    commit e415b469, which added creation of
    an index using an extremely expensive index function.  That function was
    evidently meant to be applied only twice ... but the test re-used an
    existing test table, which up till a couple lines before that had had over
    two thousand rows.  Depending on timing of the concurrent regression tests,
    the intervening VACUUMs might have been unable to remove those
    recently-dead rows, and then the index build would need to create index
    entries for them too, leading to the wrap_do_analyze() function being
    executed 2000+ times not twice.  Avoid this by using a different table
    that is guaranteed to have only the intended two rows in it.
    
    Back-patch to 9.0, like the commit that created the problem.
    5b3ce2c9
vacuum.sql 1.89 KB