>> Note that it is not really that useful for benchmarking, although it does
>> not harm.
>
> That seems plenty reason to plainly reject this patch? If we end up
> unifying it'll be added via that, no?
On the contrary, my point is to add the feature beforehand so that it is
not intermixed in the large refactoring/renamings/interfacing involved in
moving pgbench expression (lexer, parser, execution) engine to front-end
utils.
--
Fabien.
