PGroonga is a PostgreSQL extension to use Groonga as the index, and make PostgreSQL fast full text search platform for all languages (such as Japanese and Chinese).

PGroonga: https://pgroonga.github.io/

Groonga: http://groonga.org/

Default values are too low for our needs.

https://github.com/citusdata/postgresql-hll

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).

The unique reason we had to build manually or own PostgreSQL with VMs instead of using Azure PostgreSQL as a service was the lack of support of proximity placement groups.

Now that you are developing flexible server options based in "normal" VM It will be great it PPG are supported so we can address the "high" latency problems we had with the service.

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.

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.

[1] https://pgtap.org/

Implement PL/.NET Core support which will allow for Stored Procedures, Triggers, and Functions in PostgreSQL to be written in .NET Core

Please include oracle "oracle_fdw" in order to support oracle connectivity

Include support for PLJAVA extension to be able to write stored procedures, triggers, functions in Java

PostgreSQL on Azure is very outdated and extremely slow. It's very much unusable like this and we ended up moving to our own PostgreSQL container that don't have these issue. Please clarify that

Machine learning, statistics and analytics for data scientists
http://madlib.incubator.apache.org/

Include neo4j_fdw foreign data wrapper for Neo4j Graph Database

Once version 13 is out, it would be good to get it supported as documentation claims azure will support every major ver (and 12 is still not supported)

Whenever the databases on one region are down, allow to failover automatically to another region without changing the connections string

It will be helpful if we have pgrepack feature in azure database for postgresql to handle bloat.vacuum full will place an exclusive lock on the table and until the vacuum full is completed the transactions related to that table will be held if the vacuum full is performed at table level.So pgrepack is the alternate option where the reorg of table can be performed with out impacting any ongoing transactions.Performing repack during the time when there are less number of transactions to that table will decrease the overhead and can be able to handle bloat in efficient way.

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.html

Provides a Foreign Data Wrapper for easy and efficient access to Oracle databases, including pushdown of WHERE conditions as well as comprehensive EXPLAIN and ANALYZE support.

We would like to shrink the allocated (max) storage when we restore a PaaS to create another environment. This would be especially interesting to create Test environments from Production environments with large unused storage (due to the provisioning of a big IOPS bandwith for performance).