Separating database users for schema management and application runtime

Hello,

We are using Synapse in our company, and for security and traceability reasons, we would like to configure Synapse with two different database users:

- Admin DB user: with full privileges (including schema modification). This user would only be used during installation and during schema upgrade operations when upgrading Synapse.

- Application DB user: with restricted privileges (only data access — no schema modification roles). This user would be used by the running Synapse application in production.

I also tested a possible workaround for this problem by:

- Running an external job with the admin DB user to perform the schema upgrade.

- Configuring Synapse itself to run with the restricted DB user (no schema modification privileges).

However, when I tried this approach, I realized that Synapse still requires a DB user with full privileges (including schema modifications) in order to start properly.

Could you please consider supporting this request of using two different DB users, or suggest an alternative temporary solution to achieve a similar separation?