Airflow in Postgres 15+ . I big ask from a database architect

[hettie-d]

Hi Community! I come from a different universe, so please forgive me if this discussion belongs to another place (and, in this case, please direct me to where it belongs). At my day job, I am a Postgres database architect, and one of many things I am trying to maintain in my organization is setting up permissions in Postgres properly, including no usage of public schema for anything except system functions and extensions, and avoiding creating multiple databases on one instance.
Many of my customers use Airflow, and I hoped that with Postgres 15 finally removing the special status of the public schema, it would be easier for me to enforce best permissions practices. However, I found out that the Airflow for PG 15+ successfully overcomes this limitation:). I know that your code never references the schema directly, so technically speaking, all objects can be created in a different schema with the default search path modified to include it, but then we still have an issue with multiple databases on one Postgres instance.
My ask is, would you guys be open to switching of using different schemas instead of different databases for PG 15 and up? And if not, can I still direct users to install Airflow in scheas different from public? Could this create problems for future upgrades?

Thank you! Hettie D.