Aaron Dwi

Some on the net: 1. postgres use snapshot isolation semantic (pending transaction, committed, etc) and checking it against the xmin/xmax value of each row, a good blog is [here](https://brandur.org/postgres-atomicity) 2....

Seems this behavior also affect per column lock behavior. While [reading](https://github.com/kelindar/column/blob/main/column.go#L188) the value , it only locks the column, but on txn code, especially for delete and insert, doesnt have...

Separating read-only and read-write transaction definitely gonna makes the API clearer about the guarantee, I totally support this. As for per page (row shard?), how would it handle insert? As...

For isolation level, typical read-focused databases benefit from `snapshot` isolation level? As long running and repeated queries gonna have same values read. These gonna need like creation/deletion (a la postgres...

> It could be of fixed size, something like a pre-allocated slice and then use range reduction and modulo to figure out the shard index Ah okay, with predefined max...