Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Add Teleport Sync option to force a primary key to exist rather than creating a ctid

Answered
David Hayward User
  • Edited

In the case where tables are recreated on each refresh, if a primary key is missing, the logic to automatically create a ctid will result in unwanted and unexpected MAR spikes. In this case, it would be preferred that Fivetran throw an error rather than attempting to automatically create a ctid. It would be great to have a configuration option to enable this behaviour.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Amanda Wong User

    Hi David,



    This request highlights a valid pain point for tables that are frequently recreated and lack a primary key. Automatically generating a ctid can indeed lead to unintended MAR increases. We understand the need for greater control and transparency in these cases, and agree that having a configuration option to throw an error instead of auto-generating a unique key would help prevent unexpected usage spikes.



    Your feedback is noted and we're reviewing ways to expose more explicit control over primary key handling in Teleport Sync. We will update this thread once we have more information on prioritization or next steps.



    Thanks,

    Amanda