[destination-postgres] when internal table name is larger than 63 chars data get mixed up

[ogirardot]

Connector Name

destination-postgres

Connector Version

2.0.15

What step the error happened?

During the sync

Relevant information

When an original table name is already pretty long for example two tables

• arrival_pack_arrivalpacknotification_stacklist_exclude
• and arrival_pack_arrivalpacknotification_stacklist_include

then for both tables the underlying airbyte internal table will be truncated to :

airbyte_internal.target_cdc_raw__stream_arrival_pack_arrivalpacknotification_sta

creating corruptions and missing data as the final tables (that have names compatible with the 63 char hardcoded limit of postgresql) will be empty for one table and containing too much data for the other. (especially when both tables have the same schema)

Relevant log output

No response

Contribute

• Yes, I want to contribute

[octavia-squidington-iii]

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.