pogreb icon indicating copy to clipboard operation
pogreb copied to clipboard

Embedded key-value store for read-heavy workloads written in Go

Results 20 pogreb issues
Sort by recently updated
recently updated
newest added

Hi Team Need to know whether pogreb can support TB of data in the data store? And retrieve more than 500k values for a specific hash key using prefix iteration?...

I just realized that `index.numKeys` is a 32-bit uint, and there's `MaxKeys = math.MaxUint32` 😲 I think it would make sense to change it to 64-bit (any reason why we...

Hi, from documentation its clear that storage can work with multiple goroutines inside one singleton application. But can it work in scaled applications? For example, i have N instances of...

Hi, its really fast. Do you plan to develop any type of replication?

enhancement
wontfix

We are recently running into this problem which prevents the database from growing. Every time we call `db.Put` we get this error message: ``` truncate D:\Database\main.pix: The requested operation could...

windows

More details at https://github.com/akrylysov/pogreb/issues/22. Key size=16, value size=1. Writing 1M items on Linux - 16 sec. Writing 1M items on Mac - 14 sec. Writing 1M items on Windows -...

windows

It will be great if key/value will have expiration timestamp in milliseconds, therefore compaction could drop such values. It is not quite easy though: for optimimizations segment metadata could have...

enhancement

I read the code and documentation and wanted to ask if there is a specific reason why you are discarding the old index files and always recreating them? It sounds...