From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written} |
Date: | 2023-10-31 14:11:03 |
Message-ID: | ZUEK9+J55o6Fhoxl@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 31, 2023 at 08:17:52AM +0900, Michael Paquier wrote:
> Thanks for the input. I was looking yesterday if this code was
> available somewhere, but couldn't find it.. Until this morning:
> https://gitlab.com/depesz/explain.depesz.com.git
Well, the parser itself is https://gitlab.com/depesz/Pg--Explain/ :)
> And.. It looks like things would become better if we change
> "shared/local" to "shared", because the parsing code seems to have an
> issue once you add a '/'. All the fields in I/O Timings are
> considered as part of a Node, and they're just included in the output.
> Now, pasting a plan that includes "shared/local" drops entirely the
> string from the output result, so some information is lost. In short,
> imagine that we have the following string in a node:
> I/O Timings: shared/local write=23.77
>
> This would show up like that, meaning that the context where the
> write/read timings happened is lost:
> I/O Timings: write=23.77
>
> If we switch back to "shared", the context would be kept around. Of
> course, this does not count for all the parsers that may be out
> there, but at least that's something.
Well, if it's possible to deduce what is the meaning in given line,
I can add the logic to do the deduction to parser.
Also, I want to say that I appreciate being looped in the discussion.
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-10-31 14:52:12 | Re: Typo in "43.9.1. Reporting Errors and Messages"? |
Previous Message | Nazir Bilal Yavuz | 2023-10-31 13:57:57 | Re: Show WAL write and fsync stats in pg_stat_io |