Final Notice: Update to PostgreSQL Replication Mode
Scheduled for May 1, 08:00 UTC - May 4, 08:00 UTC
Subscribe to Updates
Scheduled
As communicated in an email notification earlier this year, we are finalizing the retirement of the legacy SYNCHRONOUS replication mode. To ensure continued stability, all remaining PostgreSQL clusters will be automatically migrated during their first scheduled maintenance window after May 4, 2026.
What is changing?
- Automatic Migration: Your cluster will be transitioned to ASYNCHRONOUS mode.
- Impact: You will experience a brief restart during the maintenance window. While you may see improved write performance, please note that ASYNCHRONOUS mode prioritizes speed over strict data acknowledgment.
Action Required for Strong Consistency
If your workload requires a zero-data-loss guarantee, you must manually upgrade to STRICTLY_SYNCHRONOUS via the API no later than May 1, 2026:
- Scale Replicas: Increase your cluster to 3 or more replicas.
- Update API: Set the synchronization mode to STRICTLY_SYNCHRONOUS.
Affected services: Database as a Service (DBaaS)
Location: Global Services
What is changing?
- Automatic Migration: Your cluster will be transitioned to ASYNCHRONOUS mode.
- Impact: You will experience a brief restart during the maintenance window. While you may see improved write performance, please note that ASYNCHRONOUS mode prioritizes speed over strict data acknowledgment.
Action Required for Strong Consistency
If your workload requires a zero-data-loss guarantee, you must manually upgrade to STRICTLY_SYNCHRONOUS via the API no later than May 1, 2026:
- Scale Replicas: Increase your cluster to 3 or more replicas.
- Update API: Set the synchronization mode to STRICTLY_SYNCHRONOUS.
Affected services: Database as a Service (DBaaS)
Location: Global Services
This scheduled maintenance affects: Global Services (Database as a Service (DBaaS)).