-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
BLOB type is not preserved by replication #8044
Comments
I suppose it could be easily done by a separate tag e.g. |
Segmented BLOBs has its own usage. I'll vote against their dropping. |
I would not vote for the abolition of segmented BLOBs, but rather for changes to the type of default BLOBs. By default, BLOBs are streaming, but if you really want to, then we make them segmented. Segmented BLOBs have only one use - to store lists of objects of the same size. In other cases, they have no advantages over streaming ones. |
Size of objects may vary but yes, preserving boundaries between them is a useful feature. The same way in network world stream-oriented TCP is mostly used but message-oriented UDP still keep a niche. |
Stream BLOBs become segmented in target database.
The text was updated successfully, but these errors were encountered: