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.
-
zhparser extension for Chinese Full Text Search
We would like to be able to use https://github.com/amutu/zhparser in order to implement Chinese Full Text Search.
8 votes -
PGAudit extension
Add PGAudit extension
24 votesstarted ·
AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
pgAudit is now in public preview on Azure Database for PostgreSQL. Thank you for your support of this feature.
For more information: https://docs.microsoft.com/azure/postgresql/concepts-audit
Best,
Rachel, on behalf of the Azure Database for PostgreSQL team -
Ability to scale between different tiers
Right now, it doesn't seem to be possible to scale from Basic to Standard. Would be good if that was possible.
23 votesneed-feedback ·AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
Today we support migration between General Purpose and Memory Optimised tiers. We don’t have an automated migration between either of those tiers and the Basic tier.
Please share in the comments whether you need a migration between Basic and GP/MO, and do add details on why.
Best,
Rachel on behalf of the Azure Database for PostgreSQL team -
The ability to set collation on db-create
It would have been great if the user could choose collation on first-time set-up.
11 votes -
Configurable autovacuum
Our database is in use, in reading and writing, 24 hours per day through batch elaborations and online transactional operations. In our scenario, the auto vacuum is dangerous because it can slow down operations in the wrong moment of the day causing low answer times or even unavailability of our web application.
For this reason, we decided to turn off the auto vacuum and manage manually the maintenance routine of our tables: we use pgagent to schedule daily vacuum analyze of our tables and manually run vacuum full on large tables when needed (eg. their size on disk is too…
15 votes -
Support for tds_fdw
https://github.com/tds-fdw/tds_fdw
This is a PostgreSQL foreign data wrapper that can connect to databases that use the Tabular Data Stream (TDS) protocol, such as Sybase databases and Microsoft SQL server.
11 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.
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 -
agensgraph extension
Support graph extension to postgresql
7 votes -
MADlib
Machine learning, statistics and analytics for data scientists
http://madlib.incubator.apache.org/5 votes -
Transactional DB with Analytics
AWS announced an analytics extension to Aurora for MySQL with postgreSQL to follow:
https://aws.amazon.com/blogs/aws/new-parallel-query-for-amazon-aurora/" ...you can run a mix of analytical and transactional queries simultaneously on the same table while maintaining high throughput for both types of queries. "
This would be a tremendous feature that my company could exploit at large scale.
1 vote -
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 -
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 -
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 -
Post PostgreSQL Version Updates
Could Azure announce beforehand when version updates will be applied to Azure Database for PostgreSQL? For instance, updates are posted when PHP gets updated (https://azure.microsoft.com/en-us/updates/june-2018-version-updates-to-php/).
1 vote -
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 voteunplanned ·AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
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. -
BDR
we want multi-master-replication for PostgreSQL
6 votes -
Support pg_freespacemap extension
Support pg_freespacemap extension for examining the free space map (FSM)
2 votes -
Support pg_visibility extension
Add the pg_visibility extension
1 vote -
6 votes
- Don't see your idea?