What looks compelling about the PostgreSQL offering as compared to AWS RDS is that it looks like you get a PostgreSQL cluster rather than a single database in a shared cluster. At least reading the documentation for creating a DB implies that (https://docs.microsoft.com/en-us/azure/postgresql/quickstart...).
For me, it might remove some blockers to moving some clients to a cloud managed database solution that had always been there with AWS RDS. If that follows through and pays off for having a proper PostgreSQL super user in the database environment available for use (what I really want), that can make certain things much more do-able (brings new things you have to watch out for, too, but... pick your battles).
Thank you for your feedback. We indeed offer a whole server (database cluster) and you can create multiple databases in it and have full control of the resources allocated to that cluster.
The admin user provisioned for the server is not a full superuser, but it is close to that. We are trying to find the right set of permissions to provide to our customers without jeopardizing our ability to manage this server for you. Please submit your feedback here: https://feedback.azure.com/forums/597976-azure-database-for-... if you see a problem with the permissions.
macieksarnowicz is shadowbanned for whatever reason, but he answered:
Thank you for your feedback. We indeed offer a whole server (database cluster) and you can create multiple databases in it and have full control of the resources allocated to that cluster.
The admin user provisioned for the server is not a full superuser, but it is close to that. We are trying to find the right set of permissions to provide to our customers without jeopardizing our ability to manage this server for you. Please submit your feedback here: https://feedback.azure.com/forums/597976-azure-database-for-... if you see a problem with the permissions.
We do not support automatic autoscale at this point, but it is definitely a feature we will be considering in the future. For now, you can scale on-demand in the portal or using Azure CLI.
it cannot do autoscale up and down now. But i think you can query for usage metrics and trigger a scale up/down with azure cli/powershell. This is a good feature we should have later in the public preview
What makes you think that in RDS you are part of a "shared cluster"? I believe that with RDS, your database instance runs on EC2 instance(s) dedicated to you.
The nature of the limitations AWS impose on the administrative database user account, especially because they are focused on an individual database rather than the cluster.
Shared or not is absolutely an assumption on my part. If they're spinning up an individual cluster for you, then some of the restrictions on RDS don't make much sense to me. They make more sense if it were shared.
Unfortunately, for most of the clients I work with, the limits (shared or not) are show-stoppers so I've only dealt with building a system backed by AWS RDS/PostgreSQL once and the need to dive into the underlying mechanics just wasn't there at the time.
Indeed, not only can one create multiple databases on one RDS instance, but it's also OK start an RDS instance with no user database at all, and create it later.
We're heavily using multiple databases on a single Postgres RDS. Yes, occasionally it's annoying not having a true superuser, but now they've improved it so you can still have 'fake superuser' reserved connections it's ok.
For me, it might remove some blockers to moving some clients to a cloud managed database solution that had always been there with AWS RDS. If that follows through and pays off for having a proper PostgreSQL super user in the database environment available for use (what I really want), that can make certain things much more do-able (brings new things you have to watch out for, too, but... pick your battles).