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.
-
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 -
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.
5 votes -
Ability to restore to same database name
Ability to run a point in time restore to same database name rather than restoring to a new instance.
5 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
5 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 -
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.
4 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
4 votes -
Native Python and R support - extensions plpythonu, plpython2u, plpython3u
Please support extensions plpythonu, plpython2u, plpython3u so functions etc. can have Python code.
Similar request for R support with extensions like PL/R
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 -
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 -
Add service tag feature to whitelist a specific Azure service in Azure Database for PostgreSQL firewall
At the moment, Azure Database for PostgreSQL firewall can only be configured to "Allow Trusted Azure Services" and the whitelisting of IPs/IP ranges.
There are several scenarios where customers want to provide access to only a specific Azure service without configuring the IPs/IP ranges as depending upon the service, the number of IPs can be 100+ that is unwieldy and unmanageable to add.
Due to security reasons, customers can not allow access to all Azure Services to the DB.
One of the examples, Azure Function app running on Dynamic SKU. When the function makes an outbound call to the DB,…
3 votes -
pgrouting for flexible server
Please add pgrouting extension supported on Azure Database for PostgreSQL Flexible Server (already present on Single Server).
3 votes -
Ability to grant a database user replication privileges
We set up a Debezium Kafka Connect connector with Azure Postgres as the source and will be doing so across many of the databases on the server in order to replicate the data in Postgres to other systems. For security reasons (i.e., principle of least privilege), we'd prefer to not use the database admin user for replication, but unfortunately we are forced to do so because replication privilege is only available for the server's admin user. From the Debezium documentation, this is what we'd like to do https://debezium.io/documentation/reference/connectors/postgresql.html#postgresql-permissions.
Ideally, we could work with Azure support to grant this privilege…
3 votes -
Enable pg_autofailover on postgres 12 instance
Please add postgres 12s auto failover for replicas.
3 votes -
zombodb
ZomboDB extends PostgreSQL capabilities for FTS as it works pretty nicely with Elasticsearch. It works as a native PosgreSQL extension and its support PostgreSQL versions 10.x and 11.x.
Not having it as an extensions is one of the main reasons why we don't migrate from having databases in VMs to Azure Database for PostgreSQL.
3 votes -
add cstore extension
for Columnar stores provide notable benefits for analytics use cases where data is loaded in batches
3 votes -
periods extension
The SQL 2016 standard defines a native way of handling system-versioned temporal tables. The periods extension provides this functionality for PostgreSQL versions 9.5 - 12.0, until native support is added.
https://github.com/xocolatl/periods
There is a Debian package available which can be installed:
"sudo apt install postgresql-11-periods"
The extension can then be enabled using regular CREATE EXTENSION syntax.
I would love to see this added to Azure. There is clearly demand for this functionality; the thread below suggests adding support for the temporal_tables extension and has 24 upvotes. However, that extension is now outdated compared to the much shinier periods extension.
…
3 votes -
prefix
Add prefix extension
3 votes -
Support pg_freespacemap extension
Support pg_freespacemap extension for examining the free space map (FSM)
3 votes
- Don't see your idea?