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.
-
Implement PL/.NET Core for Stored Procedures, Triggers, and Functions in PostgreSQL
Implement PL/.NET Core support which will allow for Stored Procedures, Triggers, and Functions in PostgreSQL to be written in .NET Core
6 votes -
Ability to increase max_connections
Default values are too low for our needs.
6 votes -
Add "ogr-fwd" support extension.
https://github.com/pramsey/pgsql-ogr-fdw
OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing.
6 votes -
MADlib
Machine learning, statistics and analytics for data scientists
http://madlib.incubator.apache.org/6 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 mix and match…
5 votes -
Add "pgpointcloud" extension support.
Request for support for the pgpointcloud extension in Azure PostgreSQL databases.
https://github.com/pgpointcloud/pointcloud
Would also be useful to have the optional compression features included. These require libght (https://github.com/pramsey/libght/) and lazperf (https://github.com/hobu/laz-perf).
5 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.
4 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.
4 votes -
Ability to use PG FDW to access one PG server from another w/o opening the firewall to all of Azure
I'd like a way to use Postgres foreign data wrapper (FDW) which is supported today to access one Azure DB for Postgres server from another, without opening the firewall on the first server to all of Azure.
4 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.
4 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.
4 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.
4 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
4 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 -
Support upgrading major versions via Replication
Upgrading Data via Replication is documented as a method in the PostgreSQL docs.
When creating a read replica in the Azure Portal it is not possible to change the version (I assume it uses the same version as the master).
Please allow selecting a version when creating a replica so that this upgrade method would be possible.
18.6.3. Upgrading Data via Replication
https://www.postgresql.org/docs/current/upgrading.html3 votes -
Ability to set max_locks_per_transaction
As a SaaS provider using postgresql schemas to separate clients we have a lot of tables, one set per customer schema. Some operations such as pg_dump, or schema migrations, takes locks on a lot of tables at once in the database, prior to dumping, or updating the database. For us this means that the default setting of 64 is too low and we'd like to be able to set the value ourself using parameters.
3 votes -
Pg_basebackup / Replication on-premise
It would be great if we could either use pgbasebackup as well as pgdump to take backup or the ability to replica from the Azure Master to our own db instance (either a VM on Azure or on-premise).
This would mean creating replication role slots under the Connection security tab.
3 votes -
ip4r extension
It would be great to have the ip4r extension available in the Azure Database for PostgreSQL service. We already use this extension in our self-managed psql service to use IP addresses as native objects. It is very useful for some IPAM engines like nipapd, etc.
For more information about this extension: https://github.com/RhodiumToad/ip4r
3 votes -
Stop/start server
Gaging interest for being able to stop a server when it is not being used and restart it when needed.
3 votes -
PostgreSQL in West Central US region
It doesn't appear on the roadmap. Is this planned anytime soon?
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
- Don't see your idea?