My understanding was PG only uses TOAST when the data is too large to fit in the row, and since PG compresses data before inserting wouldn't user messages be fine?
Testing with Postgres, a 2000 char random sequence doesn't result in TOASTing, but a 4000 random sequence does get TOASTed
And for kicks, 4000 chars that aren't random compress well enough that they don't end up in TOAST.
I think this limit can be adjusted, if you know that your message limit is 4000 chars its definitely a good idea.
My understanding was PG only uses TOAST when the data is too large to fit in the row, and since PG compresses data before inserting wouldn't user messages be fine?