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.
-
(Cross-region) Read replicas
Would be great to have an ability to have a master in one region (e.g. Central US) and read-only replicas in other regions (e.g. West/East US)
(renamed; merged with "active geo-replication")
55 votesWe hope to have a public preview in April-May of 2019
-
PGAudit extension
Add PGAudit extension
17 votesHi,
Thank you for your interest in this extension. Our last update mentioned that we expected it to ship this month; unfortunately we weren’t able to make it happen. In the last couple months we’ve worked on bringing our customers highly requested features including extensions like plv8 and dblink. We are continuing to work at making pgaudit available. We will provide an update once we have a more confident date; at this time our estimate is the first quarter of 2019.
Our apologies for the delay.
Best,
Rachel on behalf of the Azure Database for PostgreSQL team. -
Azure Powershell SDK support for PostgreSQL
There are great ways to manage the PostgreSQL in Azure via the Azure CLI. https://docs.microsoft.com/en-us/azure/postgresql/sample-scripts-azure-cli.
It would be great to get this possibility as well in Powershell
12 votes -
Germany
When will this be available in region germanycentral?
6 votes -
Close SSL connections gracefully
When the client closes a Postgres connection (by sending the "X" command) that uses SSL, a normal Postgres server sends SSL "close_notify" alert, thus closing the connection gracefully (client sees graceful "end of stream").
With Azure PostgreSQL, I see just a TCP RST packet, and the client sees an abrutly terminated connection.
This causes unnecessary errors with at least some Postgresql client libraries. For example, the current version of Node.js pg / node-postgres library.
5 votes
- Don't see your idea?