Postgres: Expanding column in schema tab throws "Fetch source columns failed"
Incident
Report for Fivetran
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We identified an issue for PostgreSQL connectors which resulted in schema fetch failing with a "Fetch source columns failed" error. Users were unable to expand tables or edit column configs in the Schema tab. The issue also impacted Terraform users, who experienced HTTP 400 errors when attempting to retrieve schema columns.
Timeline:
The issue began on March 11, 2026 at 01:48 UTC and was fully resolved on March 12, 2026 at 02:48 UTC.
Cause:
The issue was caused by a recent code change made to the connector.
Resolution:
Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.
Incident Summary
Description:
We identified an issue for PostgreSQL connectors which resulted in schema fetch failing with a "Fetch source columns failed" error. Users were unable to expand tables or edit column configs in the Schema tab. The issue also impacted Terraform users, who experienced HTTP 400 errors when attempting to retrieve schema columns.
Timeline:
The issue began on March 11, 2026 at 01:48 UTC and was fully resolved on March 12, 2026 at 02:48 UTC.
Cause:
The issue was caused by a recent code change made to the connector.
Resolution:
Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.
Monitoring
A fix has been implemented and we are monitoring the results.
Update
We are continuing to work on a fix for this issue.
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Database connectors (PostgreSQL).