[gunnarmorling]

Nice one, great to see this addition to the Rust ecosystem!

Reading through the README, this piqued my curiosity:

> Small or fast transactions may share the same WAL position.

I don't think that's true; each data change and each commit (whether explicit or not) has its own dedicated LSN.

> LSNs should be treated as monotonic but not dense.

That's not correct; commit LSNs are monotonically increasing, and within a transaction, event LSNs are monotonically increasing. I.e. the tuple commit-LSN/event-LSN is monotonically increasing, but not LSNs per se. You can run multiple concurrent transactions to observe this.

[sacs0ni]

Good catch, you are correct. I did mix a few things there and the statements were incorrect or at least very misleading.

To demo your point I created a gist, for myself and others to see the (commit-LSN, event-LSN) ordering in action:

https://gist.github.com/vnvo/a8cf59fc3cd8719dbea56d3bb5201f9...

I'll update the readme to reflect this more accurately. Appreciate you taking the time to point it out.