@kapa.ai I’d like to ask about the logs I encountered when syncing a BigQuery table to pgsql. It seems like the table synchronization wasn’t successful. Does anyone know the reason for this? I’m using Airbyte 0.50.50.

2024-10-22 08:04:13 normalization > Truncating data_analytics_user_wallets_records_raw_changelog (#49) to data_analytics_user__records_raw_changelog (#43)
2024-10-22 08:04:13 normalization > Truncating data_analytics_user_wallets_records_raw_latest (#46) to data_analytics_user__ts_records_raw_latest (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_audiences_creators (#47) to timed_events_launch__gn_audiences_creators (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_audiences_creators_audit_logs (#58) to timed_events_launch__s_creators_audit_logs (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_audiences_stablecoin_claim_records (#63) to timed_events_launch__blecoin_claim_records (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_audiences_transactions (#51) to timed_events_launch__udiences_transactions (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_creators_audit_logs (#48) to timed_events_launch__n_creators_audit_logs (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_creators_stablecoin_claim_records (#62) to timed_events_launch__blecoin_claim_records (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_creators_transactions (#50) to timed_events_launch__creators_transactions (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_audiences_stablecoin_claim_records_26f (#67) to timed_events_launch__oin_claim_records_26f (#43)
2024-10-22 08:04:13 normalization > Truncating timed_events_launch_campaign_creators_stablecoin_claim_records_880 (#66) to timed_events_launch__oin_claim_records_880 (#43)

Based on the logs you provided, it seems like the normalization step is truncating your table names. This usually happens when the table names exceed the maximum length allowed by the destination database, in this case, PostgreSQL. PostgreSQL has a limit of 63 bytes for identifiers, which includes table names. If an identifier exceeds this limit, PostgreSQL will automatically truncate it. However, the logs you provided and the Airbyte version you mentioned (0.50.50) are not directly mentioned in the provided knowledge sources. Therefore, I can't provide a specific solution or reason for your issue based on the provided knowledge sources. I would recommend checking the complete logs for more detailed error messages. If the issue persists, consider reaching out to the Airbyte community on their [discussion forum](https://discuss.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte/issues) for more specific assistance.