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.

https://github.com/cybertec-postgresql/pgsqueeze
pgsqueeze is an extension that removes unused space from a table and
optionally sorts tuples according to particular index (as if CLUSTER [2]
command was executed concurrently with regular reads / writes). In fact we try
to replace pg_repack [1] extension.

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

PostGIS 3.0 is currently in alpha. It adds support for parallels processing of spatial queries which drastically increases the performance of spatial queries and makes PostGIS more inline with other advanced spatial databases. Please upgrade to this version of PostGIS when it is fully released.

Would be helpful to monitor and pull statistics for queries executed on replica in Query Performance Insights. Currently its not allowed for replica's as the query data store in Azure_sys Database is also replicated from master.

for Columnar stores provide notable benefits for analytics use cases where data is loaded in batches

Users can decide when scheduled maintenance starts from in AWS.
e.g. Maintenance refers to the application of OS and database security patches.

Please be able to control schedule the maintenance in Azure Database for PostgreSQL from the users . It is problem that unexpected connection failures by maintenance in Azure Database.
For pre-planned maintenance, the convenience of users will be improved , if schedule the maintenance can be controlled.

AWS's Resource
How do I minimize downtime during required Amazon RDS maintenance?
URL: https://aws.amazon.com/premiumsupport/knowledge-center/rds-required-maintenance/?nc1=h_ls

Maintaining a DB Instance
URL: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html

As described in this issue (I won't rewrite the whole request again): https://github.com/MicrosoftDocs/azure-docs/issues/35906

Azure's postgres PaaS is broken for the enterprise without this feature. I consider lack of this option a defect, not a feature request but am logging it here as directed.

It's a perfect fit together with timescaledb-extension if you have prometheus running in AKS

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

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/

Add prefix extension

Please upgrade PostGIS 2.4 to PostGIS 2.5 on PostgreSQL 10. Several new features were introduced in PostGIS 2.5 which speeds up spatial calculations.

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.

Just wanted to upgrade the TimescaleDB extension from the current v1.1.1 to v1.3 or higher to be able to utilize the Continuous Aggregates feature.

Can the 'azurepgadmin' role be enhanced so that

ERROR: permission denied: "my-trigger-name" is a system trigger

is not encountered when executing

ALTER TABLE “my_table” DISABLE TRIGGER ALL

. The system trigger in question is one associated with a foreign key and the assocated triggers are system triggers.

It would be great if we could either use pgbasebackup as well as pgdump to take backup or the ability to replica from the Azure Master to our own db instance (either a VM on Azure or on-premise).

This would mean creating replication role slots under the Connection security tab.

RUM indexes are better suited for full-text search on PostgreSQL: https://akorotkov.github.io/blog/2018/05/21/fulltext-search-made-almost-right/.