On Thu, May 3, 2018 at 4:14 PM, Peter Geoghegan <p...@bowt.ie> wrote: > On Thu, May 3, 2018 at 3:18 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Indeed, that seems weird. Maybe tweak the test scripts so you can see >> all the objects cascaded to, and then find out what the additional >> object is? (I think also you could look into the postmaster log, >> without changing the test.)
In the case of the collate tests, these are the 17 objects I can see with ignore_system_indexes=off, once I remove the "\set VERBOSITY terse" line from the end of collate.sql: drop cascades to collation mycoll2 drop cascades to function dup(anyelement) drop cascades to table collate_test1 drop cascades to table collate_test10 drop cascades to table collate_test2 drop cascades to table collate_test20 drop cascades to table collate_test21 drop cascades to table collate_test22 drop cascades to table collate_test23 drop cascades to table collate_test4 drop cascades to table collate_test5 drop cascades to table collate_test_like drop cascades to type testdomain drop cascades to type testdomain_p drop cascades to view collview1 drop cascades to view collview2 drop cascades to view collview3 (I sorted this output in my text editor) In the case of ignore_system_indexes=on, I see the same 17 entries, in addition to these 3 (20 total): drop cascades to table collate_test23 column f1 drop cascades to table collate_test4 column b drop cascades to table collate_test5 column b Perhaps this means something to you. I find it suspicious that all 3 possibly-missing entries are "column" entries. -- Peter Geoghegan