Real Time updates limits

[ilkovulchev]

Hello,

I have enabled real time updates on my "articles" table and they work fine, with on exception however. Not all columns come in the update payload. The column containing the whole article text (article_text) does not come in the payload.

I tested by shortening the text and it worked. The policy is permissive and allows all users (the public role) to perform SELECT operations on the table without any additional conditions and since it works with shorter text, the policy should not be the issue here. The size in bytes, of the text I have in the column is 2690 and the column type is text, which from what I've read should not have a problem with this data size. Also, the standard data fetch returns the column and it's data, so the problem is only in the real time updates.

Any ideas here? What can I do to make sure all columns, even those with larger texts, arrive in the update payload?

Thank you

[GaryAustin1]

supabase/realtime#223

[GaryAustin1]

That mentions a limit for UPDATE based on the column exceeding the point Postgres uses Toast to store the data. I think that is around 2k.
Solution is to have REPLICA IDENTITY FULL set. https://supabase.com/docs/guides/realtime/postgres-changes?queryGroups=language&language=js#receiving-old-records

[ilkovulchev]

Yep, this worked, now all columns are returned. I did not know about the TOAST technique and could not find the information about the replication identity change. Maybe it can be better shown and named in the documentation, but that's a different topic.

Thanks for the help man :)