PostgreSQL Troubleshooting
Learn how to troubleshoot common issues with PostgreSQL.
Billing and MAR
Data Integrity
Errors, Warnings, and Alerts
- Alert: XMIN Frozen
- Error: Canceling Statement Due to Conflict With Recovery.
- Error: Current Transaction ID Has Moved Backwards
- Error: fivetran_replication_slot Has Last Tracked LSN
- Error: Function
aurora_version()Does Not Exist at Character 8 - Error: RDS Proxy Currently Doesn’t Support Streaming Replication Mode
- Error: Replica Cancelled Query
- Error: Replication Slot Not Found
- Error: The Connection Attempt Failed (Direct Connection Method)
- Error: The Connection Attempt Failed (SSH Tunnel Connection Method)
- Error: Unable to Connect to Database. Unhandled Classified Exception
- Error: Unable To Establish Connection With the Database
FAQ
How To
- Change Your Source From a Primary Database to a Replica Database Without Triggering a Historical Sync
- Ensure Fivetran Has Access to Additional Required System Columns
- Migrate My Logical Replication Connector From the
test_decodingPlugin to thepgoutputPlugin - Migrate to a New Database Without Performing a Re-Sync
Setup and Configuration
- Can I Switch From XMIN to Logical Replication Without Problems or Re-sync?
- How to Fix Tables Without Permission to Sync in PostgreSQL
- Why Can’t I Find and Set the Parameters
logical_replicationandwal_sender_timeoutUsing the Command-Line Interface (CLI)? - Why Is Logical Replciation With The
test_decodingPlugin No Longer an Incremental Update Option?
Syncs
- Does Fivetran Sync the
spatial_ref_sysTable? - Excessive WAL Build Up
- PostgreSQL Connectors Not Capturing Deletes
- Data Replication to BigQuery Takes a Long Time
- Stuck Replication Slot
- Why Did My Logical Replication Connector Time Out?
- Why Does the Connector Take a Long Time To Execute a Query?
- Why Is My Connector Not Syncing Data Using Teleport or XMIN Update Method?
- Why Is My PostgreSQL Replication Slot Timing Out?