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
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 Powershell15 votes
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.
Rachel on behalf of the Azure Database for PostgreSQL team.
Support TimescaleDB extension to postgresql
We’ve been working with TimescaleDB team to enable it in Azure Database for PostgreSQL service. We expect TimescaleDB extension to be available to customers of our service worldwide in 6-8 weeks from now.
Nik on behalf of the Azure Database for PostgreSQL team
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")59 votes
We hope to have a public preview in April-May of 2019
- Don't see your idea?