Would it be a good idea to add TRACK_IO_TIMING as an option to @PostgreSQL's EXPLAIN which would override the GUC?
#3 means EXPLAIN options are already becoming a big mess (not allowed enough characters for that).
Please retweet after voting.
-
-
I see like a repeatable ~0.5% overhead of io timing being enabled, and a 0.9% overhead when *disabling* all the intel "make your processor slower" safety measures.
-
To be clear, I think we probably should enable it by default. Just think it's a) not free b) a separate discussion from having an EXPLAIN knob.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.