In AWS when using dblink, you can use loopback IP 127.0.0.1 as hostaddr when you are using cross database queries. When we migrate from AWS PostgreSQL to Azure Database PostgreSQL, we need to point the hostname to either the instance IP or server name. Hopefully this will be a new feature so that we can do the migration without changing the our codes every time we migrate to another server. For more details, here's the case ID 120031124003015.

To be able to script the creation of a PostgreSQL Database, it could be great if it was possible to set the Azure AD admin with an API or Az CLI.

Thanks,

ZomboDB extends PostgreSQL capabilities for FTS as it works pretty nicely with Elasticsearch. It works as a native PosgreSQL extension and its support PostgreSQL versions 10.x and 11.x.

Not having it as an extensions is one of the main reasons why we don't migrate from having databases in VMs to Azure Database for PostgreSQL.

It would be nice if PGSQL 12 (including on-by-default JIT extensions) were available as an option.

Currently Microsoft only allows TimescaleDB 1.3.2. Please add 1.6.0 as an option.

I wan to use debezium postgresql connector to my Azure database for postgresql . For that I need to set wal_level to logical but I dont find such server parameter.

PostgreSQL 12 has been GA for over 4 months now. Any indication on when it will be supported?
Version 12 contains new features like case-insensitive grouping, better connection security and various improvements that will improve scalability and performance of Large partitioned tables.

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

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.

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

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.

Add prefix extension

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.

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.

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

Even though Azure DB for PostgreSQL provides secure connection, Applications on ARO needs to access Azure DB for PostgreSQL via internet.

Currently, VNET for ARO doesn't allow any modification, therefore, there is no option avoiding going through internet when applications connect to Azure DB for PostgreSQL.

There is no point in deploying a DB container on ARO. The user needs to consider how to manage DB.

If ARO allows modifying VNET creating Service endpoint for Azure DB for PostgreSQL, it could provide more secure route and low latency connections as well.

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