That seems reasonable to me. I think my only real goal there is to eventually be able to dump a json description of what an op is waiting on and that seems adequate. -Sam On Fri, Jul 12, 2019 at 8:43 AM kefu chai <tchaikov@gmail.com> wrote:

sorry for the double post. forwarding to the correct list.

On Fri, Jul 12, 2019 at 9:16 PM kefu chai <tchaikov@gmail.com> wrote:

...

hi Sam,

as you know, i am working on replicated write. and, i think we need to make it an optional phase in ClientRequest::PGPipeline, but i am not quite sure about how we should represent it as a blocking step using dump_detail()

currently, my plan is to add a Blocker for wrapping 1 * local_txn + m * replicated_txn. and print them as - a tid, - a local return code - an array of {peer:pg_shard_t, last_complete_on_disk:eversion}

does this make sense to you?

-- Regards Kefu Chai

-- Regards Kefu Chai