Bruce Momjian schrieb am 08.10.2021 um 17:21:
However, I also need to ask how the wait event information, whether tracing or sampling, can be useful for Postgres because that will drive the solution.
I guess everyone will use that information in a different way. We typically use the AWR reports as a post-mortem analysis tool if something goes wrong in our application (=customer specific projects) E.g. if there was a slowdown "last monday" or "saving something took minutes yesterday morning", then we usually request an AWR report from the time span in question. Quite frequently this already reveals the culprit. If not, we ask them to poke in more detail into v$session_history. So in our case it's not really used for active monitoring, but for finding the root cause after the fact. I don't know how representative this usage is though. Thomas
