Track I/O timing for temporary file blocks in EXPLAIN (BUFFERS)
authorMichael Paquier <michael@paquier.xyz>
Fri, 8 Apr 2022 02:27:21 +0000 (11:27 +0900)
committerMichael Paquier <michael@paquier.xyz>
Fri, 8 Apr 2022 02:27:21 +0000 (11:27 +0900)
commitefb0ef909f605817da6b77c1f3fef0a24457ec16
treecc85a34ce3c1918a439f69e3e6f0bab1191cd486
parentdafae9707ab7e7079ce1ba22cebda4557d0cbaf3
Track I/O timing for temporary file blocks in EXPLAIN (BUFFERS)

Previously, the output of EXPLAIN (BUFFERS) option showed only the I/O
timing spent reading and writing shared and local buffers.  This commit
adds on top of that the I/O timing for temporary buffers in the output
of EXPLAIN (for spilled external sorts, hashes, materialization. etc).
This can be helpful for users in cases where the I/O related to
temporary buffers is the bottleneck.

Like its cousin, this information is available only when track_io_timing
is enabled.  Playing the patch, this is showing an extra overhead of up
to 1% even when using gettimeofday() as implementation for interval
timings, which is slightly within the usual range noise still that's
measurable.

Author: Masahiko Sawada
Reviewed-by: Georgios Kokolatos, Melanie Plageman, Julien Rouhaud,
Ranier Vilela
Discussion: https://postgr.es/m/CAD21AoAJgotTeP83p6HiAGDhs_9Fw9pZ2J=_tYTsiO5Ob-V5GQ@mail.gmail.com
doc/src/sgml/ref/explain.sgml
src/backend/commands/explain.c
src/backend/executor/instrument.c
src/backend/storage/file/buffile.c
src/include/executor/instrument.h
src/test/regress/expected/explain.out
src/test/regress/sql/explain.sql