That's quite some constrained use case. It's useful to have multiple schemas during development, and to allow the database owner to manipulate them, and not re

That's quite some constrained use case. It's useful to have multiple schemas during development, and to allow the database owner to manipulate them, and not require superuser for these tasks. It's great that this will now be the default. It will make some of my DB initialization scripts easier. Currently database owner can't even remove the public schema in a new database, because it's owned by postgres role. I regularly make differently named copies of schemas and switch between them just by altering the search path in the app, just to try out some modifications or to run testsuites. You can drop and recreate an entire schema in a single transaction without the app having to close connections to the database at all, etc. It's useful for so many things, where grouping some DB objects together has benefits.