-
Notifications
You must be signed in to change notification settings - Fork 629
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
Storing values larger than (1 << 31) - 2 (2 GB) #656
Comments
bbolt db use bucket, every bucket max 2G, badger only single max 2G, @mitar Did you find a better solution? |
Storing too big value isn't efficient. AFAIK, other database system, e.g mysql, also have limitation on value size. Do you have a real use case which needs to store a value bigger than 2GB? |
regardless of efficiency, wouldn't there be a limit in Golang's slice sizes? You'd have to store it in a []byte somehow. In which case you might want to shard it across several keys anyway. |
There is no plan to support configuring the the max value size. Please reopen this issue if you have a strong justification. |
Currently bbolt has a hard-coded limit on value size of 2 GB. Could this be increased or made configurable? It seems to me that this is just to support mmap on 32 bit systems and there is really no design limitation why not to support larger values?
On my system, I have:
So a bit less than 2^47 (128 TiB) could be the max limit for mmap on my system.
The text was updated successfully, but these errors were encountered: