Here I collect my learnings on running PostgreSQL in Azure.

PostgreSQL

Database Replication

Azure Load Testing

Code Sample

Mirroring for Azure Database for PostgreSQL in Fabric

Limitations

  • Currently, Mirroring doesn’t support Azure Database for PostgreSQL flexible server behind an Azure Virtual Network or private networking.
  • You need to update your Azure Database for PostgreSQL flexible server firewall rules to Allow public network access, and enable the Allow Azure services option to connect to your Azure Database for PostgreSQL flexible server.
  • Active transactions continue to hold the write ahead log (WAL) truncation until the transaction commits and the mirrored Azure Database for PostgreSQL flexible server catches up, or the transaction aborts. Long-running transactions might result in the WAL filling up more than usual. WAL on source Azure Database for PostgreSQL flexible server should be monitored so that storage does not fill up.
  • The source Azure Database for PostgreSQL flexible server can be either a General Purpose or Memory Optimized compute tier. Burstable compute tier is not supported as source for mirroring.

Load Testing

Azure Load Test Setup using Terraform

Aurora Replica Lag

See Replication with Amazon Aurora

As a result, all Aurora Replicas return the same data for query results with minimal replica lag. This lag is usually much less than 100 milliseconds after the primary instance has written an update. Replica lag varies depending on the rate of database change. That is, during periods where a large amount of write operations occur for the database, you might see an increase in replica lag.