Azure Database for PostgreSQL

We would love to hear it! Please take a few minutes to submit your idea or vote up an idea submitted by another Azure Database for PostgreSQL customer. All of the feedback you share in these forums will be monitored and reviewed by the Azure Database for PostgreSQL engineering team. By suggesting or voting for ideas here, you will also be one of the first to know when we begin work on your feature requests and when we release the feature.
Remember that this site is only for feature suggestions and ideas! If you have technical questions please try our documentation, MSDN forum or StackOverflow.

Do you have an idea or suggestion based on your experience with Azure Database for PostgreSQL?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Provide a list of available sku-name values by region

    The quickstarts and walkthroughs make reference to the sku-name parameter in the az postgres server create command, but there doesn't seem to be any documentation about how the name is constructed and whether every sku is available in every region. It might be good to have "get-sku-names" cmdlet (or whatever the cli equivalent is) that would return all available skus, possibly with an optional region argument.

    At least, the documentation should say "The sku-name parameter consists of 3 parts: Tier (B for Basic, GP for General Purpose, MO for Memory Optimized), Compute (Gen4 or Gen5), and Scale (1-32 vCores) -for…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback

    We have updated the documentation on the quickstarts and the tutorials to include examples of the syntax, and a reference to the regions and pricing tier page for guidance about allowed combinations.

    See this section: https://docs.microsoft.com/en-us/azure/postgresql/quickstart-create-server-database-azure-cli#create-an-azure-database-for-postgresql-server

    The additional feature request of having a cmdlet generate valid values is currently unplanned.

    Thanks,
    Rachel on behalf of the Azure Database for PostgreSQL.

  2. allow to login with the real username instead of username@{server_name}

    our product running not only in Azure, but also in AWS and on-premises, the PostgreSQL on both of them don’t need to add ‘@{server_name}’ after the real username.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Better grouping of server parameters

    Would be great if server parameters were logically grouped together (rather than just being sorted alphabetically). For example, timeout settings together, logging settings together etc.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Database for PostgreSQL

Feedback and Knowledge Base