[destination-postgres] index name breaking syncs

[tate-button]

Connector Name

destination-postgres

Connector Version

latest

What step the error happened?

During the sync

Relevant information

You guys are already aware of this, I'm just opening another issue in hopes it gets prioritized for the destination team.

#49582
#45941
#45345

Relevant log output

2026-01-28 13:55:44 destination ERROR main i.a.c.i.u.ConnectorExceptionHandler(handleException):68 caught exception! org.postgresql.util.PSQLException: ERROR: cannot open relation "air_dtv_stg_raw__stream_okc_successionplan_okc_external_source_"
  Detail: This operation is not supported for indexes.

Contribute

• Yes, I want to contribute

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11085

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will help with initial triage.

I'll review your issue and:

• Ask clarifying questions if needed
• Provide immediate guidance if available
• Escalate to the appropriate team if this requires engineering attention

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/77aeb5240dca4e6bbde7738f780f5461

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi @tate-button, thank you for reporting this issue!

I can confirm this is a known bug related to PostgreSQL's 63-character entity name limit causing collisions between table names and index names during sync operations. You've correctly identified the related issues:

• airbytehq/airbyte#45345 - The original tracking issue (still open)
• airbytehq/airbyte#49582 - A duplicate report
• airbytehq/airbyte#45941 - A community fix attempt that was closed in favor of a CDK-level fix

The root cause is that when stream names and namespaces are long enough, the truncation logic creates identical names for both the raw table's index and the temporary table, causing PostgreSQL to fail with the "cannot open relation... This operation is not supported for indexes" error.

I'm escalating this to our internal oncall team for prioritization review. I'll update this issue with a tracking link shortly.

---

This message is generated from Devin.ai (internal session link).

[devin-ai-integration]

I've escalated this to our internal oncall team for prioritization review: airbytehq/oncall#11085

The team will review this and follow up on the status of the CDK-level fix that was planned. Thank you for your patience!

---

This message is generated from Devin.ai (internal session link).