I’m thinking about a feature for the special key space where you can read a transaction’s read conflict range and write conflict range for debugging or logging purposes.
I realized this has a weird interaction with the set_versionstamped_key feature. If a transaction sets a versionstamped key, then its write conflict range is unknown until commit time.
My first reaction was to just disallow reading your own write conflict range for transactions that use set_versionstamped_key, but I’m curious what other people think would be the right thing to do here? Maybe the read should block until the write conflict range is known?