The public schema of a managed postgres database cannot be dropped, nor can you revoke create/update privileges. This is because the schema owner is postgres and we cannot use the postgres or any superuser. Dropping or restricting access to the public schema is a common step in hardening postgres. [1]

Amazon RDS PostgreSQL DB has an elegant solution to this problem that doesn't require superuser:

In short they support creating databases from a template where the owner of the public schema is rdsadmin. DigitalOcean could provide equivalent behavior where doadmin owns the public schema.

Could we get that capability or something equivalent? Thank!

[1] hardening postgres: https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058%3A_Protect_Your_Search_Path#Do_not_allow_users_to_create_new_objects_in_the_public_schema