On Sat, Nov 3, 2018 at 8:52 PM Andrey Lepikhov <a.lepik...@postgrespro.ru> wrote: > I applied your patches at top of master. After tests corrections > (related to TID ordering in index relations DROP...CASCADE operation) > 'make check-world' passed successfully many times. > In the case of 'create view' regression test - 'drop cascades to 62 > other objects' problem - I verify an Álvaro Herrera hypothesis [1] and > it is true. You can verify it by tracking the > object_address_present_add_flags() routine return value.
I'll have to go and fix the problem directly, so that ASC sort order can be used. > Some doubts, however, may be regarding the 'triggers' test. > May you specify the test failures do you mean? Not sure what you mean. The order of items that are listed in the DETAIL for a cascading DROP can have an "implementation defined" order. I think that this is an example of the more general problem -- what you call the 'drop cascades to 62 other objects' problem is a more specific subproblem, or, if you prefer, a more specific symptom of the same problem. Since I'm going to have to fix the problem head-on, I'll have to study it in detail anyway. -- Peter Geoghegan
