Setting ignore_system_indexes=off in postgresql.conf has the effect of making almost all regression tests fail during a "make installcheck". This is unsurprising, since warnings are emitted all over the place. However, some of the specific ways in which it fails *are* surprising.
I see the following regressions.diff, for the create_view tests: *************** *** 1711,1714 **** DROP SCHEMA temp_view_test CASCADE; NOTICE: drop cascades to 27 other objects DROP SCHEMA testviewschm2 CASCADE; ! NOTICE: drop cascades to 62 other objects --- 1725,1732 ---- DROP SCHEMA temp_view_test CASCADE; NOTICE: drop cascades to 27 other objects DROP SCHEMA testviewschm2 CASCADE; ! NOTICE: drop cascades to 63 other objects ! WARNING: using index "pg_toast_2618_index" despite IgnoreSystemIndexes ! WARNING: using index "pg_toast_2618_index" despite IgnoreSystemIndexes ! WARNING: using index "pg_toast_2618_index" despite IgnoreSystemIndexes ! WARNING: using index "pg_toast_2618_index" despite IgnoreSystemIndexes Why should the drop cascade to 63 objects rather than 62 because I've set ignore_system_indexes=on? I know that the order of objects is unspecified/unstable for the verbose DETAIL output of CASCADE, but that's rather a different thing to the total number of objects affected. The same thing happens to the collate tests: *************** *** 668,671 **** -- \set VERBOSITY terse DROP SCHEMA collate_tests CASCADE; ! NOTICE: drop cascades to 17 other objects --- 676,679 ---- -- \set VERBOSITY terse DROP SCHEMA collate_tests CASCADE; ! NOTICE: drop cascades to 20 other objects -- Peter Geoghegan
