-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large TOASTable rows lead to crash loop #1076
Comments
@KyleAMathews The problem is not the boolean column but the large text value you have there. Postgres stores that value separately from the row itself (it's called TOAST). When Postgres streams changes on the logical replication stream to Electric, it does not include "toasted" values if they are unchanged. Electric is not prepared to deal with that because it uses full row data for conflict resolution, e.g. when a row gets deleted in one place but needs to be resurrected in response to an update. I can't think of any workaround for this right now. |
Hmm gotcha. I guess I'll split the read info to another table then for now. |
Informative thread on TOAST https://twitter.com/gwenshap/status/1770209083225981418 |
@KyleAMathews might be worth renaming the issue to something like "Large TOASTable rows lead to crash loop" for easier lookup as we're probably not closing this soon. @alco would setting the column |
unchanged_toast
getting odd crash. I have a boolean column and I'm trying to update it from false to true and it's triggering some sort of crash, start, crash loop
Screenshot from browser
From electric:
The text was updated successfully, but these errors were encountered: