Planned PostgreSQL server restart (e.g., configuration change, patch). Cloud provider maintenance window performing a failover. pg_ctl stop or pg_terminate_backend called by an administrator

Step 1: Check if the shutdown was planned — review maintenance logs or cloud provider events.. Step 2: Add retry logic with backoff in pipelines to reconnect after the server comes back up.. Step 3: Use a highly available setup (read replicas, Multi-AZ) to minimize downtime impact.. Step 4: Set up monitoring alerts for admin shutdowns in MetricSign or CloudWatch.

High severityconnectivity

Power BI Refresh Error:
57P01

What does this error mean?

The server is shutting down and terminated the connection. Typically occurs during planned maintenance or restarts.

Common causes

1Planned PostgreSQL server restart (e.g., configuration change, patch)
2Cloud provider maintenance window performing a failover
3pg_ctl stop or pg_terminate_backend called by an administrator

How to fix it

1Step 1: Check if the shutdown was planned — review maintenance logs or cloud provider events.
2Step 2: Add retry logic with backoff in pipelines to reconnect after the server comes back up.
3Step 3: Use a highly available setup (read replicas, Multi-AZ) to minimize downtime impact.
4Step 4: Set up monitoring alerts for admin shutdowns in MetricSign or CloudWatch.

Frequently asked questions

How do I prevent 57P01 errors in automated pipelines?

Add retry logic with exponential backoff, validate data quality before loading, and monitor pipeline failures in MetricSign to catch this error early.

Official documentation: https://www.postgresql.org/docs/current/errcodes-appendix.html