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.
-
Support for PGroonga
PGroonga is a PostgreSQL extension to use Groonga as the index, and make PostgreSQL fast full text search platform for all languages (such as Japanese and Chinese).
PGroonga: https://pgroonga.github.io/
Groonga: http://groonga.org/
3 votes -
Execute SQL scripts during ARM Template Deployments
After deploying a postgreSQL service using an ARM template, in order to configure my databases, roles, etc., I have to execute a script after I have deployed the service.
I'd like a way to include a SQL script at time of deploying my ARM template.
3 votes -
PostgreSQL in West Central US region
It doesn't appear on the roadmap. Is this planned anytime soon?
3 votes -
Better support for automation of installation in ARM Template / PowerShell
We massively deploy PostgreSQL instances. We (for exemple) need to automatically deploy configuration (for instances log_* parameters). It's possible to modify configuration with AZ commands. The other automation tools don't have the required functionality:
* ARM Template cannot deploy instances with a set configuration.
* Python2 should provide the necessary tools via azure.mgmt.* but is not very well documented (it's still in preview)
* PowerShell as no options for that. (and very few means to interact with Postgres in general).
In general, the support for postgres is bad in automation tools (and the feature coverage not uniform). We have to…
3 votes -
pgTAP support for application testing
We are working on migrating our app to Azure, and our app has unit/regression tests with using pgTAP [1].
I would like Azure PostgreSQL to support pgTAP to allow us for application compatibility test.
3 votes -
Firewall option: Allow access from a specific Azure resource
While the option to allow access to all Azure services is nice, I'd much rather be able to control what resources can reach my server on a more granular level.
The vnet integration is excellent, but many Azure resources (I'm thinking specifically of Data Factory at the moment) aren't integrated with vnets, for various reasons.
3 votes -
Globally Unique/Custom Domain Names
Procedurally generated uniqueness should be added to Domain Names to ensure that a namespace will remain available across Azure subscriptions. Users should not have to generate a globally unique server name. Something like “<server name>.<some hash>postgres.database.azure.com” where <some hash> is globally unique and provided by Azure.
3 votes -
Allow customization of space and IOPS for logs
To allow for workloads that require verbose logging levels like DEBUG, it would be nice to be able to set (purchase) additional space or IOPS dedicated to storage of logs.
3 votes -
3 votes
-
URL encode PostgreSQL connection strings
The string I got initially was as follows:
postgres://user@postgre-resource-name:password@host:5432/database
Because @ sign appears twice, some tools like pg_dump were confused. The issue was solved by URL encoding the first @:
postgres://user%40postgre-resource-name:password@host:5432/database
3 votesneed-feedback ·
AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
Thanks for using Azure Database for PostgreSQL.
Where are you requesting that we display this url encoded version? You mention that you got the first string – was this from one of our documents? Do let me know so we can update it. Also, you can directly use the GitHub issues commenting system to request changes to Azure documentation on a document page.
Thanks,
Rachel on behalf of the Azure Database for PostgreSQL team -
POWA - PostgreSQL Workload Analyzer (or alternative)
Support for POWA or another performance analyzer would be nice. https://github.com/dalibo/powa
3 votesneed-feedback ·AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
Thank you for your interest in Azure Database for PostgreSQL.
Monitoring solutions that don’t have to be added as an extension are possible alternatives. Workable solutions query the server’s statistics through a low-privileged user role. Possible examples are pghero, pgwatch2.
Please do let us know if POWA specifically is needed and any additional comments.
Thanks,
Rachel on behalf of the Azure Database for PostgreSQL team -
Ability to shrink storage when restoring
We would like to shrink the allocated (max) storage when we restore a PaaS to create another environment. This would be especially interesting to create Test environments from Production environments with large unused storage (due to the provisioning of a big IOPS bandwith for performance).
2 votes -
Stop/start server
Gaging interest for being able to stop a server when it is not being used and restart it when needed.
2 votes -
Target for Data Factory (ADF)
Data Factory supports PostgreSQL and Azure PostgreSQL as sources. Please add them as targets.
2 votes -
Support for Ultra SSD SKU configuration
For performance critical workloads and large volumes of data, storage access latency is critical. Please support a Ultra SSD SKU configuration.
2 votes -
Provide actual memory being used (in GB) in Azure Monitor
Provide actual memory being used (in GB) in Azure Monitor in addition to % memory used. The customer scenario is for the Persona of a QA/Test professional. Actual memory used is much more useful than % used as it related to determining the quality of a product / service. % used is tailored to SRE/Ops persona.
2 votes -
Enable shutdown (deallocate equivalent) for Postgres when not in use.
For non-production environments it would be a helpful cost saving feature to be able to 'turn off' / deallocate Azure Databases (of all types not just postgres) when they are not in use.
While the prevailing logic would suggest that non-production environments should be destroyed when not in use, this is sometimes not convenient or practical when environments are required on (relatively) short notice and DB content sizes are relatively large
2 votes -
Correct count of Postgres connections in Portal
We use the Azure postgres database and shows the connection count in our monitoring setup. We just realized that the connection count shown in the Azure Portal is not the same as Postgres repots. We had over 170 connections at one time, while the Portal showed approx. 20 connections
2 votes -
Add DNS management to firewall rules configuration
Usually pg_hba.conf accepts DNS names so you can use i.e. my.address.ip for ***.***.***.***. In Azure portal you can input only numeric IP addresses but this presumes you have staic public IP address. Allowing DNS management you would be able to use Dynamic DNS solving non static public IP address problem.
2 votes -
Support pg_freespacemap extension
Support pg_freespacemap extension for examining the free space map (FSM)
2 votes
- Don't see your idea?