Hmm not sure if something changes for Postgres con...
# advice-data-ingestion
l
Hmm not sure if something changes for Postgres connectors but over the weekend my entire schema replication list was changed to only bring in a few tables and stop replicating and reset every other table...
Yeah, oddly it just triggered a
*ERROR* i.a.w.DefaultReplicationWorker(run):169 - Sync worker failed.
And then somehow the entire schema was changed to only replicate one table. Has anyone experienced anything similar before? Not sure how to debug granted it's a backend error but a frontend symptom ...
And we were not replicating this table before the error occurred, which makes it more strange
Nvm, determined the root cause
b
hey lucas! glad to hear you resolved the issue. what ended up being the root cause?
ah yikes! thank you for sharing what happened. Was just checking if there were any action items that we needed to pursue on the OSS side, but sounds like you have it all sorted
l
Hmm not exactly. This thread has more context: https://airbytehq.slack.com/archives/C038KM9NF7Z/p1660585903637209
I think we can certainly improve the Airbyte docs to make this security risk clearer. I'd be happy to open an issue on this this week and PR to update the docs
b
got it and yes feel free to file a GH issue/contribution whenever you’re ready