Hey Jose, thanks!
I think you’re referring to the fact that things like e.g. sequences can commit out-of-order, is that right? I actually wrote about this last week!
For a given row, the WAL will return updates in order. But indeed across rows sequence values may come in out-of-order. We think that strict ordering by row is what people want when they want ordering, but if anyone has use cases where they need strict ordering across rows/keys let me know.
The “transactional guarantees” bit in my post was about ensuring that inserts into messages only happen if some other database operation you’re performing also succeeds (both commit together).
