...PostgreSQL 9.5...
`DROP SCHEMA blah;` reports all the dependent objects and advises to `DROP SCHEMA blah CASCADE;` ...
Will DROP ... CASCADE traverse the entire dependency tree for each of the dependent objects (potentially dropping something unintended), or will it stop at the first level and balk at any new transitive dependencies?
All the dependent objects listed by `DROP SCHEMA blah` are fair game to be dropped, but if I add CASCADE I don't necessarily want to have it go beyond that initial list without my say-so.
The alternative is to drop each one in the list individually without CASCADE-- a tedious task I'd rather short-cut, but in a non-reckless manner ;) ...
CG