C GG <cgg0007@xxxxxxxxx> writes: > ...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? The former. However, the list of dependencies it's showing you as potentially dropped already includes transitive dependencies; there aren't going to be "new" ones unless somebody is adding things concurrently. If you're feeling paranoid, you could always do begin; drop ... cascade; and then look at the reported list of objects before deciding whether to commit or roll back. regards, tom lane
