> Thanks. index_including.sql embodies all sorts of anti-patterns
> for testing: use of very generic object names that could conflict
> with concurrent test scripts, constant dropping and re-creation
> of objects ensuring that the overhead per useful test is as high
> as possible, etc.
Thanks for pushing it. This one seems like another nice opportunity to
clean up testing anti-patterns. Apart from the two mentioned, are there any
other anti patterns here? And any previous attempts/discussions to make it
better? I'm happy to start a new thread to collect the things that can be
improved, not just for this test but for any others as well (if any), and
work incrementally on making the tests better. Let me know.