pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: track_io_timing logging: Don't special case 0 ms. 2+ messages / 1 participants [nested] [flat]
* pgsql: track_io_timing logging: Don't special case 0 ms. @ 2021-08-27 20:35 Peter Geoghegan <pg@bowt.ie> 0 siblings, 0 replies; 2+ messages in thread From: Peter Geoghegan @ 2021-08-27 20:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org track_io_timing logging: Don't special case 0 ms. Adjust track_io_timing related logging code added by commit 94d13d474d. Make it consistent with other nearby autovacuum and autoanalyze logging code by removing logic that suppressed zero millisecond outputs. log_autovacuum_min_duration log output now reliably shows "read:" and "write:" millisecond-based values in its report (when track_io_timing is enabled). Author: Peter Geoghegan <pg@bowt.ie> Reviewed-By: Stephen Frost <sfrost@snowman.net> Discussion: https://postgr.es/m/CAH2-WznW0FNxSVQMSRazAMYNfZ6DR_gr5WE78hc6E1CBkkJpzw@mail.gmail.com Backpatch: 14-, where the track_io_timing logging was introduced. Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/bda822554b96c6564911df95fcb898d6c30efe46 Modified Files -------------- src/backend/access/heap/vacuumlazy.c | 15 +++++---------- src/backend/commands/analyze.c | 15 +++++---------- 2 files changed, 10 insertions(+), 20 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: track_io_timing logging: Don't special case 0 ms. @ 2021-08-27 20:35 Peter Geoghegan <pg@bowt.ie> 0 siblings, 0 replies; 2+ messages in thread From: Peter Geoghegan @ 2021-08-27 20:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org track_io_timing logging: Don't special case 0 ms. Adjust track_io_timing related logging code added by commit 94d13d474d. Make it consistent with other nearby autovacuum and autoanalyze logging code by removing logic that suppressed zero millisecond outputs. log_autovacuum_min_duration log output now reliably shows "read:" and "write:" millisecond-based values in its report (when track_io_timing is enabled). Author: Peter Geoghegan <pg@bowt.ie> Reviewed-By: Stephen Frost <sfrost@snowman.net> Discussion: https://postgr.es/m/CAH2-WznW0FNxSVQMSRazAMYNfZ6DR_gr5WE78hc6E1CBkkJpzw@mail.gmail.com Backpatch: 14-, where the track_io_timing logging was introduced. Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/6a1095234e0fcfa5c2f618c7c841e8ffe3c6c712 Modified Files -------------- src/backend/access/heap/vacuumlazy.c | 15 +++++---------- src/backend/commands/analyze.c | 15 +++++---------- 2 files changed, 10 insertions(+), 20 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-08-27 20:35 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-08-27 20:35 pgsql: track_io_timing logging: Don't special case 0 ms. Peter Geoghegan <pg@bowt.ie> 2021-08-27 20:35 pgsql: track_io_timing logging: Don't special case 0 ms. Peter Geoghegan <pg@bowt.ie>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox