Re: Expose options to explain? (track_io_timing)

I think the theory for track_io_timing being PGC_SUSET is that if the superuser turned it on, no one should be able to turn it off.  

But I don't see an argument for the other way around, that no one should be able to turn it on locally of the superuser left it at the default of off.

So I think the real behavior we would want is that anyone can turn it on in their session, and can also turn it off provided it was turned on by them in the first place.  But there is no machinery in the GUC code to do that, which is probably why it wasn't done.  I meant to work on that for this dev cycle, but I never dug into how to implement the "provided it was turned on by them in the first place" part of the requirement.  And how would this be expressed generically? Some notion that the default value can be a floor or ceiling which the user can alter in one direction, and reverse that alteration. PGC_SUSET_FLOOR and PGC_SUSET_CEILING?

Anyway, if we are going to solve this for track_io_timing, I think it would be better so solve it in a way that it can also be used by pg_stat_statements, as well as EXPLAIN.  But maybe that doesn't make sense, as you need to be a superuser to call pg_stat_statements_reset() anyway.

Cheers,

Jeff