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.
That seems like a separate discussion to to me. Independent on the GUC being enabled by default, it's still quite worthwhile to be able to control EXPLAIN ANALYZE's overhead with options like this.
-
-
The overhead is negligible in nearly all cases, we only don’t have it enabled by default because on some platforms, most of which are gone now, it can be expensive...
-
It's really not negligible when you either have fast IO and do a lot of IO, or rely on the kernel side page cache. Even on a modern platform. The overhead of EXPLAIN's TIMING is obviously higher - that's why it's OK to implicitly turn in on in EXPLAIN ANALYZE.
- 2 more replies
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.