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!